What has been done, and what is still wrong.

What this site does

Every interactive element is reachable and operable from the keyboard, and focus is always visible. The four things a reader operates here — the coverage matrix, the check inspector, the code samples and the glossary filter — are built on native elements, so each works fully before any script runs.

Colour is never the only carrier of meaning: the status cells in the coverage matrix pair their colour with a mark and a text label for assistive technology. Motion is decoration throughout and is removed entirely, not shortened, when the operating system asks for reduced motion.

• Single h1 per page, headings in order
• Visible focus, skip link, landmark regions
• Status conveyed by mark and text, not by colour alone
• Text reflows to 320 px without horizontal scrolling
• Prefers-reduced-motion removes every animation

Known limitations

The coverage matrix and the API resource table scroll horizontally on a narrow screen. A table of five markets against six capabilities does not reduce to a single column without losing the comparison that is its only purpose, so the honest answer is that it scrolls.

The diagrams carry a text alternative that describes what they show, but a reader using a screen reader gets the summary rather than the full structure. Where a diagram carries information that exists nowhere else, that is a defect; where it restates the page, it is a reasonable compromise. We believe the latter is currently true throughout, and would like to be corrected if it is not.

The capture SDK

The part of the platform a player actually meets is held to the same target. The capture flow is operable without a pointer, every control is labelled, and a player who refuses or cannot use a camera is offered a file-upload path rather than a dead end.

The honest limitation is the liveness step, which asks for a short sequence of head movements. Where a player cannot perform it, the operator's manual review path is the alternative, and the SDK surfaces that rather than looping.

Tell us

If something here is unusable, write to [email protected] and say what you were trying to do and what happened. A specific report of a single broken thing is more useful than a general audit, and it gets a reply from someone who can fix it.