Accessibility

We aim to meet WCAG 2.2 Level AA. This page says what has been built for that, what we know is imperfect, and how to tell us when something does not work, instead of simply asserting that the site is accessible.

What is built in

• A “skip to main content” link as the first focusable element on every page.
• One h1 per page and headings in order, so a screen reader’s outline matches the visible structure.
• Landmarks (header, navigation, main and footer) and labelled navigation regions.
• Visible focus outlines on every interactive element, never removed for appearance.
• Every form field has a real associated label, not a placeholder standing in for one, and errors are announced rather than only shown in color.
• FAQ blocks use native disclosure elements, so they open with the keyboard and are readable with JavaScript unavailable.
• Text alternatives for meaningful images; original diagrams carry a title and description equal to the question they answer; purely decorative graphics are hidden from assistive technology.
• Text and interface colors chosen to meet AA contrast against their backgrounds.
• Layouts reflow to a single column on small screens and at high zoom without horizontal scrolling; the mobile menu is a native disclosure that works with the keyboard.
• Motion and transitions are disabled for anyone whose system requests reduced motion.

Where we know there are limits

The bot check on the request form is provided by Cloudflare and is not something we control the accessibility of. If it prevents you from submitting a request, that is exactly the kind of barrier we want reported, and we will take your request another way.

Some guidance pages carry long tables of comparative information. These are marked up as real tables with header cells so they can be navigated correctly, but a long table is demanding to read in any assistive technology. If you need the content of one in a different form, ask.

Telling us about a barrier

Use the contact form and describe the page, what you were trying to do, and what happened, including the browser and assistive technology if you know them. We treat this as a defect report, not feedback. If the form itself is the barrier, say so in whatever way you can reach us and we will provide the information or take the request another way.