Accessibility

Last updated 29 August 2026

Our commitment

We want everyone to be able to read and use this site, including people who browse with a screen reader, navigate by keyboard alone, need larger text, or need less movement on screen.

Conformance

The Web Content Accessibility Guidelines (WCAG) define requirements for making web content more accessible. This site is built to meet WCAG 2.2 Level AA. The measures below are how that is done.

What has been done

  • One h1 per page and a heading order that never skips a level.
  • Landmark structure with a single main region, a labelled navigation, and every section named by its own heading.
  • A skip link to the main content as the first focusable element.
  • Every interactive element reachable and operable by keyboard, with a visible focus indicator that meets the contrast requirement.
  • Text and interface colours chosen to meet contrast minimums in both the light and dark appearances the site supports.
  • Decorative graphics hidden from assistive technology; the diagram that carries meaning has a text description of what it shows.
  • Movement is decorative only. The site honours the operating system's reduce-motion setting, and the page remains fully readable if the animation never runs at all.
  • Text is real text, never an image of text, and reflows without loss of content down to a narrow phone width and up to 200% zoom.
  • Form fields have persistent visible labels, are grouped where related, and report errors in text rather than by colour alone.

Display options

Every page carries a Display options control in the bottom corner, with settings for appearance (light, dark or follow your system), text size, increased contrast and reduced motion. These are first-party settings stored only in your browser, they apply across every page of the site, and they are read before the page paints so nothing flashes at the wrong size or in the wrong appearance.

We deliberately do not use a third-party accessibility overlay or toolbar. Overlays frequently interfere with the assistive technology people have already chosen and configured for themselves.

Compatibility

The site is built to work with current versions of Safari, Chrome, Firefox and Edge, and with the screen readers commonly paired with them, including VoiceOver on macOS and iOS, NVDA and JAWS on Windows, and TalkBack on Android. It does not require JavaScript to be readable; scripts add motion and the display options only.

Technical specifications

Accessibility relies on HTML, CSS, SVG, WAI-ARIA and JavaScript, and on the combination of a browser and any assistive technology installed.

Feedback

If you meet a barrier on this site, please tell us through the inquiry form and describe the page and what happened. We treat access problems as defects and aim to respond within five working days.