Skip to content

Accessibility

Accessibility statement for chrimes.dev

This statement applies to content published on chrimes.dev. We design and build the site ourselves. Accessibility is part of the service we sell — it’s also, reasonably, something we think our own site should get right.

Compliance status

This website is designed to conform to Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. As of our last review we consider the site to be fully conformant against the criteria listed.

“Fully conformant” means that the site meets the accessibility standard without any exceptions we’re currently aware of. If you find something that doesn’t, please tell us — see reporting an issue.

Our approach

  • WCAG 2.2 AA is the target baseline for every page. We treat conformance issues like bugs — the feature isn't done until they're fixed.
  • Semantic HTML first. ARIA only when semantic HTML can't do the job. Landmarks, headings, lists and form controls built from the elements the browser already understands.
  • Keyboard accessible throughout — tab order is logical, every interactive element has a visible :focus-visible state, and a skip-to-content link is the first focusable element on every page.
  • Colour contrast meets 4.5:1 for body text and 3:1 for non-text UI components across both light and dark colour schemes.
  • Motion respects the user's OS-level reduced-motion preference; no parallax, no auto-playing carousels.
  • Forms have explicit labels, `aria-invalid` on error states, an `aria-live` region for status messages, and a clear text alternative for anything communicated by colour alone.

How we test

Industry research is consistent that automated testing catches about 30–40% of WCAG issues. We run the automated checks, then manually test the rest — which is where most real problems turn up.

Automated

  • axe-core via Lighthouse on every deploy preview
  • ESLint eslint-plugin-jsx-a11y during development
  • Our own accessibility quick-scan run against the live site regularly

Manual

  • Keyboard-only navigation top-to-bottom of every page (Tab, Shift+Tab, Enter, Space, Esc)
  • Screen-reader walkthroughs using VoiceOver (macOS / iOS) and NVDA (Windows)
  • Zoom to 200% and 400%; reflow at 320px viewport width
  • Operating-system high-contrast / forced-colours mode checked for every interactive element
  • prefers-reduced-motion enabled to confirm animations are suppressed

Known issues

We aren’t currently aware of any accessibility issues on chrimes.dev. If that changes — either from our own testing or a report from a visitor — we’ll list the issue here along with a target fix date. Honest issue tracking is a better signal than a statement that claims perfection.

Reporting an accessibility issue

If you encounter a problem not listed on this page, or believe we’re falling short of WCAG 2.2 AA, please let us know:

adam@chrimes.dev

We aim to respond to reports within two working days and to fix confirmed issues within ten.

Enforcement

chrimes.dev is a private-sector business and isn’t subject to the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. Accessibility in the UK private sector is governed by the Equality Act 2010, enforced by the Equality and Human Rights Commission. If you contact us about an accessibility issue and aren’t satisfied with our response, that’s where you can take it next.

Technical information

Standard
WCAG 2.2, Level AA
Tech stack
Next.js 16, React 19, Tailwind CSS v4
Assistive tech tested
VoiceOver (macOS & iOS), NVDA (Windows), keyboard only
Last reviewed