Skip to content
Accessibility

Built in, not bolted on.

Contrast, focus states and keyboard paths were part of the first components we built rather than a pass before launch. This page says what that means in practice, and what is still wrong.

Last reviewed 21 September 2026

The standard we work to

We aim at WCAG 2.2 Level AA. We have not commissioned an independent audit, so we describe this as what we build towards rather than a certification we hold.

Keyboard and focus

Every interactive control is reachable with a keyboard, and the focus indicator is a two-pixel outline that follows the shape of whatever it is on. On dark panels the ring switches to a light one so it stays visible.

Each page starts with a skip link, because the header holds several tab stops before the content begins. Interactive targets are at least 44 by 44 pixels.

Reading and contrast

Body text is checked against its background rather than chosen by eye. Where text sits over a photograph, the surface behind it carries its own ground, because an image is never a guaranteed contrast surface.

Headings are ordered rather than picked for size, so a screen reader can use them to move through a page. Images that carry meaning have descriptions; images that are decoration are marked as such and skipped.

Motion

If your system asks for reduced motion, transitions and scrolling animations are turned off rather than shortened. Nothing on the site depends on an animation to become usable.

What is not right yet

Naming these is more useful than claiming they do not exist.

  • The header runs past the edge of the screen between roughly 768 and 1200 pixels wide, which can cause sideways scrolling on a tablet or a small laptop. It is a layout fault in the navigation bar and it is on the list.
  • Several destinations — including publishing controls and account recovery — are still placeholders. They are marked as unavailable rather than left as controls that silently do nothing.
  • We have not yet tested the whole site with a screen reader end to end. Individual components were built and checked against one; the full journey has not been walked.

If something here blocks you, tell us and it moves up the list. Write to us through the contact page. A report that names the page and what you were trying to do is the most useful thing you can send.