This accessibility statement lists what has been built, not making a bare claim of compliance, since a compliance claim is not checkable and a list of specifics is. Every page leads with a skip link, uses real landmarks, carries exactly one first-level heading, and renders its content on the server so it is available before any script runs. Form controls have real labels instead of placeholders standing in for them, errors are announced, not shown only in colour, and the stop-use warning on the request form is announced as an alert when it appears. Tables use header cells and scroll inside their own containers. Every diagram carries a title, a description and a visible caption, with labels as real text. The known limits are listed below, and a barrier you hit is treated as a defect instead of as a feature request.
We build this site to meet WCAG 2.2 AA. This page says what has been done, where the known limits are, and how to tell us when something does not work, not making a bare claim of compliance.
What has been built in for accessibility
- A skip link to the main content as the first focusable element on every page
- Semantic landmarks, header, navigation, main and footer, on every page
- One
h1per page and headings that descend in order - Every form control has a real associated label, not a placeholder standing in for one
- Errors are announced to assistive technology instead of shown only in colour
- The stop-use warning on the request form is announced as an alert when it appears
- Tables use header cells with scope, and scroll inside their own container on narrow screens
- Every diagram is an SVG with a title, a description and a visible caption
- Diagram labels are real text, so they scale and can be read by a screen reader
- Text and interface colours are chosen to meet AA contrast in light and dark
- Focus is visible on every interactive element, and focus order follows reading order
- FAQ blocks use native disclosure elements, so they work with the keyboard and without JavaScript
- The page content is server-rendered, so it is available before any script runs
Known limits
The spam protection on the request form is provided by Cloudflare Turnstile, a third-party component whose accessibility we do not control. If it prevents you from submitting a request, tell us through the request service form and we will take the request another way.
The diagrams convey their information through both the drawing and its written description. If a diagram’s description is not sufficient to understand the point it makes, that is a defect worth reporting, and it will be treated as one.
Reporting a barrier
Send it through the request service form with the page address, what you were trying to do, and what happened instead. Tell us what you are using, browser, screen reader, magnification, if you can, as that commonly makes the problem reproducible. We treat an accessibility barrier as a defect , not a feature request.
Review
Updated September 27, 2026.
What has been built, and where the limits are
Stated as specifics, not as a compliance claim, so you can check any row of it yourself.
| Area | What is in place | Known limit |
|---|---|---|
| Keyboard | Skip link first, visible focus, order follows reading order | None known |
| Structure | Landmarks on every page; one h1; headings in order | None known |
| Forms | Real labels, errors announced, stop-use warning as an alert | The spam-protection widget is third-party |
| Tables | Header cells with scope; scroll inside their own container | Wide tables still scroll horizontally on a phone |
| Diagrams | SVG with title, description and a visible caption | Report any caption that does not carry the point |
| Colour | AA contrast targeted in light and dark | Report any combination that fails for you |
| Without JavaScript | All page content is server-rendered | The triage tool and FAQ search need it |
| Disclosure widgets | Native elements, keyboard and screen-reader friendly | None known |