What we have actually done.

Implemented

• Semantic HTML and heading order

  Pages are built from real landmarks, lists and headings, with one h1 per page and no levels skipped. A route sweep checks the heading structure on every page before a deploy.

• Keyboard operation

  Every control is reachable and operable by keyboard. The stage selector is a real tab interface with arrow-key navigation, the FAQ uses native disclosure elements, and menus close on Escape.

• Visible focus

  A consistent focus ring is applied to every interactive element, at a contrast that survives the dark background.

• Contrast

  The color palette was measured rather than eyeballed. Body-size blue text uses a lighter step than display text for that reason, and a separate script checks contrast across the site — a route sweep once passed a build with ten failures because nothing was broken, only too dim.

• Reduced motion

  Respected throughout. The hero diagram draws its finished state once and never starts an animation loop; transitions elsewhere are reduced to near-zero.

• Content does not depend on JavaScript

  Company facts, service descriptions, the FAQ answers and the assessment questions are all server-rendered text. If scripts fail to load, the site renders unanimated rather than blank — content fails visible, deliberately.

• Text, not pictures of text

  The labels in the hero diagram are real HTML elements over the canvas, so they can be selected, translated, zoomed and read aloud.

• Forms

  Every field has a real associated label, errors are announced, and a failed submission never reports success.

Known limitations

• The site is built to WCAG 2.2 AA as a working target. Every page is checked with automated tooling across three viewports, and the menus, tabs and the assessment are tested by driving real keyboard input. Testing with an actual screen reader, and an independent third-party audit, have not been done — so we describe what we check rather than claiming conformance.
• No screen reader testing has been done. Automated tools catch roughly a third of real accessibility problems, so a clean automated run is a floor rather than a result — if something reads badly in NVDA or VoiceOver, we would genuinely like to hear about it.
• The hero diagram is decorative. It is marked as such and the page means the same thing without it — but it is a canvas, and it will not be described by a screen reader beyond the labels around it.
• Legal documents on this site are generated from a shared kit and are styled rather than authored here. Structural issues inside them have to be fixed in the kit.