Accessibility

The target

WCAG 2.2 Level AA.

How it is tested

Every template on this site — the home page, the scan form, the sign-in page and the confirmation page — is run through axe-core at a 390px phone viewport and a 1440px desktop viewport before release. The most recent run returned no blocking violations on any of the four.

Contrast is measured rather than judged by eye. Each text and surface pair in the design system carries its computed ratio as a comment beside it, and the smallest ratio anywhere in the interface is 4.78:1 against a 4.5:1 requirement. Colour is never the only channel: every severity carries its word and a notch count as well as its hue.

What that buys you

• Every interactive element is reachable and operable from the keyboard, with a visible focus ring.
• A skip link to the main content, and real landmarks rather than a soup of divs.
• Motion respects prefers-reduced-motion. Turn it on and every animation renders its final state immediately — nothing is hidden behind a transition that never plays.
• The page works with JavaScript disabled: the content is there, and the FAQ still opens.
• Form fields are labelled and sized so that focusing one does not zoom the page on iOS.

What is still open

• The report page at /scan/[id] renders from live scan data and has not been through an automated pass with a populated report in front of it. It inherits the same design system and the same measured colour pairs, but that is inheritance, not a test result, and we are not going to describe it as one.
• No screen-reader testing with real assistive-technology users has been done. Automated tools catch roughly a third of what matters, and we would rather say so than let an axe score stand in for a person.

If something is in your way

Tell us what you were trying to do and what stopped you, and we will fix it and say when. [[REAL PROOF NEEDED: contact address for accessibility reports]]