Accessibility

We build to the Web Content Accessibility Guidelines 2.2 at level AA. This page says what that means on this website specifically, and is honest about what has and has not been tested.

What this site does

• Semantic structure. One h1 per page, a heading order that does not skip levels, real landmark elements, and lists marked up as lists.
• Keyboard operation. Everything interactive is reachable and operable from a keyboard, in a logical order. A skip link is the first focusable element on every page. The mobile menu traps nothing and closes on Escape.
• Visible focus. A high-contrast focus ring is drawn on every focusable element, and it inverts on light sections so it stays visible.
• Contrast. Body and interface text is designed to meet or exceed the 4.5:1 ratio, and large display text the 3:1 ratio.
• Image descriptions. Screenshots carry alternative text describing what the screen shows, written for someone who cannot see it, not stuffed with keywords. The Engine drawing is decorative and is hidden from assistive technology; the layer names beside it are real text.
• Reduced motion. With prefers-reduced-motion: reduce set, every animation on the site renders in its final state immediately. The Engine arrives assembled on the homepage hero and stays open on the layer section, which are the states each of those needs to be readable.
• Nothing loops. The homepage sequence plays once and stops. Nothing on this site moves on its own after that, so there is no moving content to pause.
• Without JavaScript. Content is server-rendered and the entrance animations are CSS, so the pages read the same with scripting off. A noscript rule neutralises the scroll reveals so nothing is trapped behind an animation that cannot run.
• Errors on the form. A failed submission is reported three ways: a summary at the top of the form that takes focus and links to each problem, aria-invalid on the control, and a message tied to the control so a screen reader announces it with the field.
• The AI workflow explorer. Choosing a process and opening a stage are radio inputs, so the explorer works from a keyboard and with scripting off. Every stage description is in the page rather than fetched when you click.
• The Lab. The structure experiment is operated entirely with links and radio inputs, so it works from a keyboard and with scripting off. The same data is published as a table underneath it.

What we have not done

We have not commissioned an independent third-party audit of this website, and we have not carried out formal usability testing with assistive technology users on it. We are not going to describe it as certified or fully conformant on the strength of our own checks.

Tell us if something is broken

If any part of this site is difficult or impossible for you to use, we want to know, and we will fix it. Use the project form, tell us the page and what happened, and we will reply.

In the work we build

The same standard applies to what we build. Accessibility is checked continuously during the build rather than audited at the end, because it is cheap to hold and expensive to retrofit.