What we aim for

We work towards WCAG 2.2 Level AA. That is a target we keep moving towards, not a certificate we hold, and we are not going to claim full conformance. What we will do is fix things when we learn about them.

What is in place

  • A “Skip to main content” link, one <main> landmark per page, and breadcrumbs on every page below the homepage.
  • Text and interface colours checked against WCAG AA contrast ratios by calculation rather than by eye, including the primary buttons, the cookie banner and the active blog tag, each of which previously carried white text on a bright gradient at 2.4–3.7:1.
  • Keyboard operation of the navigation — including the About, Services and Use Cases drop-downs, which open on Enter or Space, close on Escape, and were previously reachable only with a mouse — plus the mobile menu and the homepage article carousel, all with a visible focus indicator.
  • Text alternatives on meaningful images; decorative graphics hidden from assistive technology.
  • A layout that reflows on small screens and when text is enlarged.
  • No forms to fill in — enquiries are by email, which means no timeouts and no validation traps.

Known limitations

Wide tables inside blog articles are now held in a horizontally scrollable container that can be panned with the keyboard, so they no longer push the page sideways. Two things we have not solved: the article carousel on the homepage has no controls below 480px, and there is no live announcement when it moves. If you hit a barrier that is not listed here, we would rather hear about it than not.

Telling us about a problem

Email [email protected] with the page address and a short description of what went wrong. If you need something on this site in a different format, ask and we will send it. We aim to reply within two business days.

Related: About · Editorial Policy