Accessibility
What we have built in, and what we have not verified.
We aim to meet WCAG 2.2 level AA. This page says what that has meant in practice and where the gaps are, rather than claiming a standard has been certified.
What is in place
- Every page is built from semantic HTML with one h1 and a heading order that does not skip levels.
- Everything usable with a mouse is usable with a keyboard, including the mobile menu, the Methods and Resources filters, and the contact form.
- Focus is always visible, and never removed without being replaced.
- Form controls have real labels. Errors appear in a summary at the top of the form, are linked to the field they belong to, and are announced when they appear.
- The contact form moves focus to the outcome after each submission, so the result is not missed.
- Animation is switched off for anyone whose system asks for reduced motion.
- Wide tables in resources scroll horizontally and can be scrolled from the keyboard.
- Page layouts work from 320px upward without horizontal scrolling.
- Decorative images carry empty alt text so screen readers skip them.
- The language selector is keyboard operable and announces the current language.
What we have not verified
- This site has not been audited by an independent accessibility organisation.
- It has not been tested with every combination of screen reader and browser. Our testing has been keyboard-first, with automated checks.
- We have not published a formal accessibility conformance statement, because we have not done the testing that would make one honest.
If something does not work
Tell us. Describe the page and what you were trying to do, and say which browser and assistive technology you were using if you can. We will fix what we can and say so if we cannot.
Report an accessibility problem