How we work

Accessibility Statement

What we have built

Charts. Every figure on this site is SVG with a descriptive aria-label and a paired data table behind a "show this figure as a table" control. No information exists only as a picture.

Tables. Row and column headers use proper scope attributes. Sticky headers do not trap keyboard focus. Sorting and filtering announce their results through a live region, so a screen-reader user learns how many rows matched rather than being left to infer it.

Missing data. Unverified values render as text reading "not verified" rather than as an empty cell, a dash or a colour. Nothing on this site is communicated by colour alone — evidence badges carry text and a shape, not just a hue.

Mobile. At a 390-pixel viewport no fee, qualifier, evidence status or source date is hidden. Tables scroll horizontally with a sticky first column rather than dropping columns.

Motion. The only animation is a drawer transition, and prefers-reduced-motion disables it. There is no autoplay, no carousel and no parallax.

Keyboard. A skip link, visible focus rings on every interactive element, and no keyboard trap. The source-ledger drawer returns focus to the control that opened it.

Structure. One h1 per page, headings in order, landmark regions, and a table of contents on longer pages.

Known gaps

We would rather list these than claim compliance we have not tested.

• No independent audit yet. The build has been checked against the criteria and tested by keyboard, but no third-party accessibility audit has been commissioned. That is scheduled before launch.
• No screen-reader testing across assistive technologies. Automated tools do not catch table semantics or announcement quality; manual testing with more than one screen reader is outstanding.
• Charts convey trend as well as value. The data table gives every number, but a reader relying on it does not get the shape of a distribution as directly as a sighted reader does. We are working on better textual summaries for the more complex figures.
• Fonts load from a third party, which can produce a flash of fallback text on slow connections. Self-hosting is planned and will remove it.

Tell us what does not work

If something on this site is difficult or impossible to use, we want to know specifically what and with what technology. Accessibility reports are treated as corrections: dated, logged, and fixed rather than acknowledged.

Contact the editorial team

Questions readers actually ask