Accessibility.

These tools should work for everyone, with a keyboard, a screen reader, a phone, large text or a dark screen. This page says how that is checked and where it still falls short.

What we aim for

Every page should meet the Web Content Accessibility Guidelines 2.2 at level AA, in the light theme and the dark one, on a laptop and on a phone. This page does not claim that the site conforms. It says what is built in, what has been checked and how, and what is known to fall short.

What is built in

  • Keyboard. Every page starts with a link that skips to its content. The menus, the theme switch and the search box (press / to open it) all work from the keyboard, and whatever has the keyboard is outlined.
  • Light and dark. Pages follow your device’s setting, and the switch in the header overrides it. Text meets the contrast the guidelines ask for in both (4.5 to 1 for ordinary text).
  • Size. No text is smaller than 12 pixels, and at a phone’s width no page scrolls sideways.
  • Charts. In the Data Explorer and the Country stories, put the keyboard on a chart and the arrow keys read it value by value; each chart’s figures are also there as a table. Chart colours were chosen by test, to stay apart for colour-blind readers, and a colour is never the only way to tell two things apart.
  • Motion. If your device asks for less motion, the fade between pages and other transitions are switched off. A map plays through the years only when you press Play.
  • Documents shared for comment. A comment can be placed with the keyboard: New comment, the arrow keys to move the marker, then Enter.
  • Report Studio. Blocks can be added and moved up and down without a mouse.

How it is checked

Before a change to the site is accepted, an automated browser opens every page on its list, more than forty of them, at a laptop width and a phone width, in both themes. A page fails if it has a serious fault against the WCAG 2.2 A and AA rules that a program can test (axe-core runs them), text smaller than 12 pixels, anything that makes it scroll sideways, or a script error.

A second script takes the routes that only a keyboard takes: opening the menus and the search box, moving a block in Report Studio, and placing a comment on a shared document. The chart colours have their own tests, for contrast and for colour-blind readers.

A program finds only some faults. It cannot tell whether a page makes sense when it is read aloud.

Where it falls short

  • No one has yet tested the site with a screen reader or with voice control and written down what they found. Until that is done, treat what a screen reader says as unchecked.
  • Maps are pictures. In the Data Explorer the figures behind a map are in the ranking beside it; in Map Studio they are the table you pasted in.
  • What the studios make. A chart, map or diagram saved from a studio is a picture with no description of its own; whoever publishes it needs to write one. A report exported from Report Studio has not been checked.
  • Shared documents are drawn as pictures of their pages, so a screen reader cannot read them there. Ask whoever shared the document for the file itself.
  • Presentations are shown as they were uploaded and have not been checked.
  • On a very narrow screen (320 pixels, or a laptop zoomed to 400%), the longest country names in some rankings break in the middle of the word.
  • The Knowledge Repository and the Grant Sharing Portal carry this site’s header and colours but are separate programs, and are not yet part of the automated checks.
  • A page made as a backdrop for a talk or an event is a moving picture first. It has keyboard controls, but a screen reader will get little from it.

Telling us about a problem

If something here does not work for you, the Centre would like to know: write to the Global Safety Evidence Centre at Lloyd’s Register Foundation through the Foundation’s contact page (opens in new tab), and say which page and what you were trying to do.

Last reviewed in November 2026.