Talk to Threatless

Accessibility statement

Where this website stands against WCAG 2.2 AA.

This website is designed to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Here is how we work towards that, how it is tested and where it still falls short.

The standard we target

We aim to conform to WCAG 2.2 (opens in a new tab) at level AA. Conformance has not yet been confirmed by an independent accessibility audit, so we describe it as a target rather than a claim.

How the site is built

  • Semantic HTML with one main heading per page, landmarks and a skip link.
  • Every interactive element works with a keyboard and shows a visible focus indicator, including on dark sections.
  • Color tokens are checked for contrast: body text is at least 6:1, metadata text at least 4.5:1 and form borders at least 3:1. Brand green is never used for small text on light backgrounds.
  • Every diagram has a text equivalent, and on small screens diagrams are rebuilt as readable step lists rather than shrunk.
  • Motion is optional: with reduced motion enabled in your system settings, animations are switched off.
  • Core content and navigation work without JavaScript. The enquiry form needs JavaScript for its abuse protection.
  • Light and dark appearances follow your system setting, and you can choose one in the footer.

How it is tested

Every page is checked automatically against WCAG 2.2 A and AA rules with axe-core, at phone, tablet and desktop widths, and keyboard behavior is tested for the menus, dialogs and form. Results are recorded in the project's test reports.

Known limitations

  • Testing with screen readers on real devices (VoiceOver, TalkBack, NVDA) has not yet been completed.
  • The conceptual diagrams are illustrations. Their meaning is available as text, but the drawings themselves are hidden from assistive technology.
  • The enquiry form is not yet connected to a monitored inbox, so it cannot yet be used to report an accessibility barrier.

Tell us about a barrier

If something on this site does not work for you, we want to know. Once enquiries are enabled, please use the contact page and tell us the page, what you were trying to do and the assistive technology you use, if any.

Statement prepared on 19 October 2026 from automated testing and visual review of this build.