Menu

Accessibility statement

The accessibility standard the index is built to, what you should be able to do on every page, known limitations, and how to report a barrier.

This site is built to WCAG 2.2 Level AA. Every build runs an automated accessibility check on one page of each page type at four screen widths, and a build fails on a violation. The site has not had an independent accessibility audit.

On every page you should be able to zoom, use a keyboard and use a screen reader, from a screen 320 pixels wide up. If something blocks you, tell us.

You should be able to zoom, use a keyboard and use a screen reader throughout

A screen reader can move through every page by its headings and landmarks, and a keyboard can reach every control. Every page provides:

  • One main heading, headings in order and landmarks
  • A keyboard route to every interactive element, with a focus ring you can see on the red header, the navy footer and in dark mode
  • A mobile menu and question-and-answer disclosures in native HTML, working without scripts
  • A visited state on links in content
  • No sideways page scroll at any width, from 320 pixels up
  • Zoom, touch targets of at least 44 pixels, and text never smaller than the site’s base small size
  • Reading text held to a comfortable line length

The site hosts its own fonts, with no third-party font service.

Colour is never the only cue

Colour contrast meets WCAG 2.2 AA in light mode and in dark mode, and the site follows your system’s light or dark setting. A status, a map legend or a chart series carries text or a marker shape as well as a colour, so you can read it without the colour.

Images carry alt text from their records. Data tables have a caption and header cells marked for assistive technology.

Known limitations are listed here and removed when fixed

These are the limitations we know about. A fixed one comes off this list.

  • Below 1024 pixels a map is for orientation only; the table linked under it selects a place.
  • A wide data table scrolls sideways inside its own region, not the page.
  • A chart is a drawing, with its table equivalent linked under it.
  • Site search runs in your browser and needs scripts; without them, the search page lists the index pages instead of an empty box.
  • The French site is partial at launch, and a French page that falls back to an English string or an English page is marked where it happens.

See what the search page shows with and without scripts.

Tell us about a barrier and we will respond

Send us the page address, what you were trying to do, and the browser or assistive technology you used. We acknowledge a report within 2 business days, the same commitment we make for a correction to the record.

Find where to send a barrier report.