What is in place
- Every control can be reached and operated with a keyboard, with a visible focus indicator, including the frame tabs, the deployment selector, the comparison sliders and the project brief. Focus does not land under the sticky header, and while the cookie notice is open, focus scrolls clear of it and Escape closes it from anywhere on the page.
- Every image has a text alternative. Diagrams and the annotated frames carry a description of what they show; purely decorative marks are hidden from assistive technology.
- Motion is optional. “Pause motion”, the second stop when you press Tab on any page, holds the whole site at rest for the rest of your visit in that tab, and pressing it again lets motion run. Visitors who ask their system for reduced motion get the same rest state without asking: every element complete, no opening animation, no rotating frames and no video loop. Nothing on the site depends on an animation having finished.
- Without scripts, every section and piece of copy is still present, and email addresses stay readable and linked. The project brief needs scripts to prepare an email or a file: without them its fields stay visible, it sends nothing, and the page gives the address to write to instead.
- Pages use one heading per level in order, named landmarks, a skip link, and language and title metadata. Text can be enlarged to 200 percent, and pages reflow to 320 pixels wide without horizontal scrolling or clipped text, also with wider letter, word and line spacing.
- The project brief explains each problem in words, moves focus to the field concerned, and marks that field as invalid for assistive technology, with the explanation attached to it.
- Video loops are silent, decorative and never carry information; the still image beneath them is the content.
What we did
In October 2026 we checked the site against WCAG 2.2 level AA by hand as well as with automated tools: every page with the keyboard alone, at 200 percent zoom and 320 pixels wide, with increased text spacing, with reduced motion, without scripts, and with the project brief’s errors as assistive technology receives them. We sampled the colours behind every piece of text the automated audit could not judge. The audit found no violations. The manual checks led to the changes above: focus kept clear of the header and the cookie notice, the “Pause motion” switch, and the error information on the brief’s fields. None of them changes how the site looks.
What we check
Every change runs an automated accessibility audit (axe-core) on every page, in a desktop and a phone-sized view, and a Lighthouse audit, accessibility included, on five representative pages: Home, Engine, Deployment, Contact and one field note. The same test suite checks that pages are complete with reduced motion and without scripts. These checks run on each change and report what they find, but publishing does not wait for them, so a problem they find is fixed in a following release. They catch many problems but not all of them; we have not commissioned an independent audit.
Known limitations
- “Pause motion” appears only when it has keyboard focus, like the skip link; there is no pause button always on screen. Pausing, or letting motion run again, reloads the page.
- The annotation labels over the imagery in the living frames and the identification cascade are short machine-style readings and part of the picture. Against the busiest parts of an image some fall below the contrast ratio body text must meet; their meaning is given in the surrounding copy, and each frame is described in text.
- The step labels above the project brief respond to a pointer only; with a keyboard, move between steps with Next and Back.
- While the cookie notice is open it can cover the very end of a page. Answer it, or press Escape, to uncover it.
- The comparison sliders can be moved by keyboard in single steps; a visitor who cannot use them still sees both images, side by side, when scripts are off.
- Some label text on dark panels is set small by design. If it is hard to read, browser zoom scales it without breaking the layout.
Tell us
If anything on this site is hard to perceive, understand or operate, write to ah@vanguarddefensesystems.com and say which page and what happened. We aim to reply within five working days and to fix confirmed barriers in the next release.