Accessibility

How we work to make this site usable for everyone

We aim for WCAG 2.2 AA. Here is how we test, what still needs work and how to tell us about a problem. Last reviewed: 22 October 2026.

Our commitment to accessibility

We aim for this website to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Accessibility is part of how we design, write and build every page, rather than a check at the end.

Accessibility is ongoing work. Pages change and new content is added, so we keep testing and fixing over time.

What we have in place

We design every page with clear headings, landmarks and a logical reading order, and a skip link lets keyboard users jump straight to the main content.

  • Menus, the search dialog, the mobile menu, tabs, question lists and forms are designed to work with a keyboard, and every focusable element shows a visible focus outline.
  • Text and form controls are designed to meet WCAG 2.2 AA contrast, including text that sits on photographs.
  • Images that carry meaning have text alternatives. Decorative images are hidden from screen readers.
  • Form fields have visible labels. If a field needs fixing, the problem is described in words next to the field.
  • Pages reflow on screens as narrow as 320 pixels and can be zoomed to 400 percent without content being cut off.
  • We respect your device's reduced motion setting, and nothing on the site moves or flashes on its own.
  • We write in plain language at about a 6th-grade reading level.

How we test

We last tested this site against WCAG 2.2 AA on 22 October 2026. We ran automated checks (axe-core) on every page at four screen widths, and we tested by hand: keyboard-only use, focus order and focus visibility, 320-pixel reflow, text spacing, reduced motion, target sizes, form error messages and the contrast of text on photographs.

Automated tools catch only some problems, so we treat manual testing as essential. We fix problems in order of how much they affect people.

Known limitations

  • The illustrative dashboards and charts are examples, not live data. They are hidden from screen readers or given a short text label, and the same information appears in the text around them. Ask us and we will explain any chart in words.
  • Wide comparison tables scroll sideways on small screens. Each one is labelled, and you can reach it with the keyboard and scroll it with the arrow keys.
  • We have not yet completed a full test with screen readers such as JAWS, NVDA and VoiceOver. If anything does not work well with your assistive technology, please tell us.

Report a problem

If you have trouble using any part of this site, email [email protected]. Tell us the page address, what you were trying to do and, if you can, the device, browser and any assistive technology you use.

We aim to reply within two business days and to fix confirmed problems as quickly as we can. If you need information from the site in another format, ask us and we will provide it.

Websites we build for clients

When we build or update websites for clients, we build to WCAG 2.2 AA and test them in the same way. We do not describe any website as fully accessible or compliant, because accessibility depends on ongoing content and changes. We tell clients what we tested, what we found and what still needs work.

When we last reviewed this

This statement was last reviewed on 22 October 2026. We review it whenever the site changes significantly.