Contact us Request a consultation Experienced a breach? 24/7 incident response

Accessibility statement

What this prototype was built and tested against, what passes, and what is still outstanding. Stated honestly, including the gaps.

Target standard

This prototype was built against WCAG 2.2 Level AA.

What was implemented and verified

  • Keyboard operation. Every interactive control is reachable and operable by keyboard, including the navigation, the accordions, the attack-path diagrams, and all form fields. The diagram nodes are focusable and respond to Enter and Space.
  • Visible focus. A 2px focus indicator with offset is applied to every focusable element and is never removed.
  • Skip link. A skip-to-content link is the first focusable element on every page and targets the main landmark.
  • Color contrast. Every text node was audited programmatically against its painted background at the AA thresholds (4.5:1 body text, 3:1 large text).
  • Reduced motion. prefers-reduced-motion: reduce disables the scroll progress bar, all reveal animations, counters, the marquee, the diagram path animation, and the alert pulse.
  • Semantic structure. One h1 per page, a logical heading order, landmark elements, and tables with captions and scoped headers.
  • Form labels. Every input has a visible, associated label. Errors are announced per field, not only in a summary, and required fields are marked in text as well as color.
  • Non-text content. Diagrams carry a descriptive aria-label; decorative imagery is hidden from assistive technology.
  • Reflow. No horizontal scrolling at any viewport width from 320px upward.

Known limitations

  • The attack-path diagrams convey their content through an accessible readout panel and node labels. A visitor using a screen reader receives the information in a different order than a sighted visitor does.
  • Testing was conducted with automated tooling and keyboard verification in Chrome. It has not yet been tested with JAWS, NVDA, or VoiceOver by a screen reader user.
  • Fonts load from a third-party service. If that request fails, the page falls back to system fonts, which changes the headline fitting.

Feedback

If you encounter a barrier on this site, tell us on the contact form. Give us the page and what happened, and we will fix it and tell you when it is done.

This statement describes the prototype as built and tested on 20 October 2026.