Accessibility
Last reviewed 10 September 2026.
This site is meant to be usable by everyone, including people using a screen reader, a keyboard only, magnification, or a browser set to reduce motion. Accessibility here is built into the markup rather than added as a layer on top, which is why you will not find a floating toolbar in the corner.
The standard we build to
We aim at the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. We are not claiming a formal audit or a certification, because we have not commissioned one. What follows is what we actually check on every build, honestly described.
What is checked before anything ships
- Structure. One page heading per page, headings in order, real landmarks, and a skip link that jumps straight to the content.
- Keyboard. Every link and button reachable and operable by keyboard, in a sensible order, with a clearly visible focus ring that is never removed.
- Images. Every illustration on this site is inline artwork, and each one is either labelled or marked decorative so a screen reader does not read out noise.
- Contrast. Body text, headings, buttons and the coloured answer boxes are all set from a palette chosen to clear the AA contrast threshold against their backgrounds.
- Zoom and reflow. The layout reflows to a single column and stays usable at 200 percent zoom and at 320 pixels wide, with no horizontal scrolling of the page body. Wide tables scroll inside their own box rather than pushing the page sideways.
- Motion. There is no animation, no autoplay and no carousel, and the small hover transitions are switched off entirely for anyone whose system asks for reduced motion.
- Almost nothing loads from outside. No external fonts, no UI widgets, no overlays and no scripts that alter the page under you. The only outside code is our host's cookieless visit counter, which draws nothing on screen and changes nothing you interact with. Everything you see is plain HTML and CSS served from this domain, which is a deliberate accessibility decision as much as a privacy one.
Known limits
- We have run automated and manual keyboard checks. We have not commissioned testing with assistive technology users, and we will not claim we have.
- The comparison sheet is a plain table, which is fine to read but not built to be filled in on screen. It is meant to be printed or copied.
- Pages link out to sources we do not control, including government and industry sites. Their accessibility is theirs.
Found a barrier
Tell us and we will fix it. Please say which page, what you were trying to do, and what you were using (browser, screen reader, magnification), because that turns a report into a repair.
We treat an accessibility report the same way we treat a wrong figure on a cost page: it gets fixed and we say that we fixed it.