Accessibility

We build to WCAG 2.2 Level AA. A feature does not ship until its primary path meets that standard, and our build fails if an automated accessibility check finds a violation on a tested page.

• Everything works with a keyboard alone, with a focus indicator you can always see.
• Status is never shown by colour alone — there is always a label and a shape.
• Text can be enlarged to 400% without losing content or function.
• Motion respects your reduced-motion setting.
• Forms explain errors in words, and you can save and come back later.
• Touch targets are at least 44 by 44 pixels.
• There are no drag-only interactions and no inaccessible CAPTCHA.
• We warn you before a session times out and let you extend it.
• An Easy Read version is available for key information.

Automated checks with Axe run on every build. Beyond that we test with keyboard only, with screen readers, at 200% and 400% zoom, on mobile, with reduced motion and in high contrast. Automated tools catch perhaps a third of real problems, so testing with people who use assistive technology is part of our process, not a substitute for it.

We will keep an honest list here of known accessibility problems and when we expect to fix them. If you find something that does not work for you, tell us and we will add it — a barrier we do not know about is one we cannot fix.