Accessibility statement
This site is partially conformant with WCAG 2.2 level AA. Four WCAG 2.2 AA failures are listed below, each with the criterion it fails and the date we expect it fixed, plus one related item recorded for completeness.
The framework treats accessibility as a competence that professionals are expected to hold. Publishing a statement here that claims more than we have tested would fail our own specification, so this page states the test date, the method and the failures.
Statement prepared 28.08.2026 · last tested 27.08.2026 · page last reviewed 30.08.2026
The whole site, including the dated framework trees and every downloadable artefact.
Some content does not fully conform. The failures are listed below rather than summarised.
Automated and manual testing across a sample from every section of the site.
Two serious, two moderate, one recorded for completeness. Each carries a remedy date.
What does not work yet, and when it will
Each issue names the WCAG 2.2 criterion it fails, where it occurs, what it means for you in practice, and the date by which we expect it remedied. If a remedy date passes without the issue closing, the date is replaced and the slip is stated rather than removed.
| Criterion | Issue and effect | Where | Severity | Remedy by |
|---|---|---|---|---|
| 1.4.3 AA | Technical Steel fails contrast at small sizes Two pages still use the lighter steel tone for supporting text below 24px, where it does not reach 4.5:1 against the paper background. The text is readable but not to the standard we set. | Statement pages, coverage map examples | MODERATE | 30.09.2026 |
| 1.4.10 AA | Wide tables scroll horizontally at 320px The register, notices and coverage map tables are wider than a 320px viewport and scroll sideways in their container. The content is reachable, but reading a row requires horizontal scrolling on a small phone. | Register, notices, coverage maps, decisions | MODERATE | 31.10.2026 |
| 2.4.7 AA | Focus indicator too faint on the navy bands The focus outline is drawn in accent blue, which is hard to see against the navy sections. A keyboard user can lose track of where they are in those bands. | Navy sections on every section landing page | SERIOUS | 30.09.2026 |
| 4.1.2 A | Filter results are not announced When a filter changes the number of results, the count updates silently. A screen reader user has no notification that the table beneath has changed and must go looking for it. | Statement index, register, notices, search | SERIOUS | 31.10.2026 |
| N/A · privacy | Web fonts are not yet self-hosted Not a WCAG failure, recorded here because it is the same piece of work. Fonts are fetched from a third-party host, which the privacy page names as an open item. | Every page | MINOR | 31.10.2026 |
Method, tools and who did it
| Automated | axe-core and Lighthouse on a sample of 14 pages covering every section and every page type. |
|---|---|
| Keyboard | Full manual keyboard pass on the sample: tab order, focus visibility, skip link, filters, forms and every disclosure. |
| Screen reader | NVDA with Firefox on Windows, and VoiceOver with Safari on macOS, on the homepage, statement index, a statement page, the register and notices. |
| Zoom and reflow | 400% zoom and a 320px viewport, checked for loss of content and for horizontal scrolling. |
| Tested by | Amara Osei, Director and chair of audit and risk, internally. No independent audit has been commissioned. |
| Date of test | 27.08.2026 · next scheduled test 27.02.2027, and after any substantial change |
No independent audit has been commissioned. Until one has, this statement is our own assessment of our own work, which is worth less than an audit and is described as such.
Decisions taken for accessibility, not despite it
If you could not use something here, tell us
Write to accessibility@aicertificationstandards.org with the page address and, if you can, the browser and assistive technology you were using. You do not need to know which criterion it fails, or use the word accessibility at all.
Escalation
Reply to our answer asking for it to be reviewed. The review is done by someone who did not write the original answer.
Write to governance@aicertificationstandards.org. Accessibility complaints are handled under the same complaint procedure as any other governance concern, and are recorded whether or not they are upheld.
You may complain to the enforcement body for accessibility in your jurisdiction at any point. You do not have to exhaust our process first.
Barrier reports and their outcomes are counted in our annual report. We do not publish the reporter's identity.