Accessibility statement
Last updated
We sell accessibility work, so this site should be easy to use for everyone. Here’s what we’ve done, how we checked it and where we know it falls short.
Our target
We aim to meet WCAG 2.2 Level A and AA for every page on this site. We haven’t had the site independently audited, so we don’t claim full conformance.
How we built and tested it
- Semantic HTML first: real headings, landmarks, buttons, links and form labels.
- A visible two-tone focus indicator on every interactive element, which works on light and dark backgrounds.
- Text and controls meet WCAG AA contrast ratios. Status and severity never rely on color alone.
- The type family, Atkinson Hyperlegible Next, was designed by the Braille Institute for readers with low vision.
- Animation is limited and respects your reduced-motion setting.
- Tested on 2026-10-07: automated checks with axe-core on every page, keyboard-only use of every page and form, zoom to 200% and 320-pixel-wide reflow, and review of the accessibility tree in Chromium.
Known limitations
- We haven’t yet completed testing with NVDA, JAWS or VoiceOver on this site. That’s next on our list.
- Screenshots in free-check results are images of third-party pages. We describe what was found in text beside them, but we can’t describe every detail of someone else’s page.
- The spam check on our forms is provided by Cloudflare Turnstile. It’s usually invisible; if it asks you to interact and you can’t, contact us another way and we’ll help.
- The AI assistant is built on an open-source chat component that we’ve adapted and tested with a keyboard. Let us know if anything about it gets in your way.
Report a barrier
If something on this site doesn’t work for you, please tell us what page and what happened. Use the contact form. We read every report and will reply with what we’re doing about it.