Legal

Accessibility Statement

Effective July 27, 2026 ยท Last reviewed July 27, 2026

Institutions are legally obliged to procure accessible technology, and a vendor who cannot answer questions about accessibility creates work for you. This page is our answer.

Conformance target

We target WCAG 2.2 Level AA. That standard underpins Section 508 of the Rehabilitation Act, Title II of the ADA as applied to public institutions, and EN 301 549 in the European Union.

The public site currently meets that target on automated and manual testing. The assessment platform launching August 15, 2026 is being built to the same target and will be tested before release rather than after.

What we test, and how

  • Automated: axe-core and Lighthouse accessibility audits run against every page.

The public site scores 100 on the Lighthouse accessibility audit.

  • Contrast: every text and background pair is checked against the 4.5:1 ratio for

body text and 3:1 for large text and interface components. We check muted text against every surface it sits on, not just white, because that is where it usually fails.

  • Keyboard: every interactive element is reachable and operable by keyboard alone,

with a visible focus indicator and a skip link to main content.

  • Structure: one h1 per page, no skipped heading levels, landmark regions, and

descriptive text alternatives on every meaningful image.

  • Motion: all animation is suppressed under prefers-reduced-motion.
  • Zoom and reflow: content reflows to 320 CSS pixels without horizontal scrolling

and remains usable at 200% zoom.

Automated tools catch roughly a third of real accessibility problems. We supplement them with manual keyboard and screen reader passes, and we would rather hear about a barrier from you than not know about it.

Known limitations

We would rather list these than claim perfection.

  • The public site has not yet been through a formal third-party audit. We intend to

commission one before the platform launch.

  • Screen reader testing to date has covered VoiceOver on macOS and iOS and NVDA on

Windows. We have not yet tested JAWS.

  • Generated PDF reports are tagged for structure, but complex data visualisations within

them are summarized in adjacent text rather than being independently navigable.

VPAT and procurement documentation

A Voluntary Product Accessibility Template (VPAT 2.5 Rev, INT edition) covering WCAG 2.2 AA, Section 508 and EN 301 549 is available on request, and will be published alongside the platform launch. If your procurement process needs it earlier, ask and we will send the current draft with its limitations marked honestly.

Reporting a barrier

If any part of the Service is difficult or impossible for you to use, tell us. Include the page, what you were trying to do, and your assistive technology and browser if you know them.

[email protected]

We aim to acknowledge within two business days and to give you a remediation timeline within ten. Where a fix will take time, we will offer a workaround in the meantime.