Accessibility statement. Our target is WCAG 2.2 AA.

We want everyone to be able to read this site and use the health check, whatever device, assistive technology or settings they use. We hold our own site to the same standard we ask of the design systems we work on.

This statement covers this website, its articles and the health check. It was prepared on 24 October 2026, updated for the new site on 25 October 2026, and will be reviewed before the end of January 2027. It is a draft under review.

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We believe the site partly meets that target today: automated checks pass, but we have not yet completed a manual audit with assistive technologies, so we do not claim full conformance.

How we test

  • Automated axe checks on every page at desktop and phone widths, in light and dark mode.
  • Scripted keyboard checks: skip link, the menus, focus order and focus that stays visible.
  • Checks that pages do not scroll sideways at 320 pixels wide, and that every page still works with reduced motion and without JavaScript.
  • Text alternatives for every diagram, written as a caption next to it.

Known issues

  • We have not yet tested the site with screen readers such as VoiceOver, NVDA or TalkBack. Some diagrams may be read in an unexpected order. Each diagram has a written description beside it.
  • Pages other than the home page are in English only for now. The Japanese home page is an AI draft that a native speaker is still reviewing.
  • On the Japanese home page, findings that come directly from the audit engine are shown in English.
  • The health check report's print and PDF output has not been checked for accessibility.
  • Linked sources on other websites are outside our control.

Tell us about a problem

If something on this site does not work for you, or you need the content in another format, use our contact form. Please tell us the page, what you were trying to do and the device or assistive technology you use. We will reply and, where we can, fix the issue or send you the information another way.

Start with a conversation about your system.

We read your system, show you what we found, and agree with your team what to fix first.