Skip to content

Accessibility statement

What we have done, what we know is imperfect, and how to tell us when something blocks you.

Last updated 1 September 2026

Our target

We aim to meet WCAG 2.2 level AA across this site. That is a target rather than a certification: we test as we build, we fix what we find, and we publish the known gaps below rather than claiming full conformance.

What we have done

  • Semantic headings in document order, so a screen reader can navigate by structure.
  • A skip link to the main content as the first focusable element on every page.
  • Visible focus indicators that are not removed by any stylesheet rule.
  • Text contrast measured against AA thresholds with axe-core across ten representative pages, including the market accent colours and the muted label colour, which both failed before we measured them and were darkened until they passed.
  • Interactive controls that work from the keyboard, with accordions and menus exposing their state.
  • Full support for prefers-reduced-motion, which disables every animation on the site.
  • Layout that reflows to 320 pixels wide without horizontal scrolling, and survives 200 per cent text zoom. Both are checked in a browser rather than asserted.
  • No content that depends on colour alone to convey meaning.

Known limitations

  • Some comparison tables in long articles scroll horizontally on narrow screens. The content is reachable by keyboard, but a table is still a harder reading experience than prose on a phone.
  • A few generated articles contain dense tables with five columns. We are gradually restructuring the worst of them into paired lists.
  • Third-party analytics, where a site owner has configured it, is outside our control for accessibility purposes. It renders nothing visible.

Accessibility in the work we deliver

We apply the same standard to client deliverables. Power BI reports we build use accessible colour combinations, include alt text on visuals, set a sensible tab order, provide keyboard-navigable interactions and are tested with a screen reader before handover. Where a client brand palette fails contrast requirements we say so and propose an accessible variant rather than shipping it quietly.

Reporting a barrier

If something on this site prevents you from doing what you came to do, tell us through the contact form, with the page and what happened. If the form itself is the barrier, the postal address on the imprint reaches us. We will acknowledge within two working days and tell you what we are doing about it, including if the answer is that it will take a while.