What this site aims for
WCAG 2.2 at level AA. That is the target rather than a certification, and the difference matters: nobody has audited this site externally, and the statement below is our own honest assessment.
What has been done
All of it verifiable from the page source.
- Every page works without JavaScript, apart from the reader, which needs it to render a PDF
- Full keyboard operation, with a visible focus outline that is never removed
- A skip link to the main content on every page
- Headings in a real hierarchy, never chosen for their size
- Text contrast at or above 4.5:1 throughout, checked rather than assumed
- Form fields with real labels, not placeholder text standing in for one
- Errors reported in text next to the thing that went wrong
- No content that moves, flashes or autoplays
- Reduced-motion preferences respected
Known limitations
The PDF reader draws pages to a canvas, which a screen reader cannot interpret. That is a property of rendering a fixed-layout document rather than something we have neglected, but it is a real barrier and we are not going to describe the reader as accessible because the buttons around it are.
If you use a screen reader, PDF to Text is the better route into a document: it extracts the text layer into a plain file your own tools can read properly. Where a document has no text layer, nothing here can help, because there is no text in the file at all.
If something here excludes you, tell us
Write to [email protected] with the page and what went wrong. An accessibility barrier is treated as a bug rather than a feature request, and it goes to the front of the queue.