Accessibility

Accessibility is a core requirement, not an add-on.

The brand guide treats it that way. The platform reflects it. This page states it. WCAG 2.1 AA is the floor — not the ceiling.

WCAG 2.1 AA · MINIMUM
Our commitments

Specifically, we commit to.

Nine specifics. Each one applies to every screen of the platform and every page of this site.

Colour-independent meaning

Every traffic light is paired with a label, an icon, and a position. Meaning is never carried by colour alone.

Contrast

All text meets WCAG 2.1 AA contrast ratios — 4.5:1 for normal text, 3:1 for large text and UI components.

Focus indicators

Every interactive element has a visible focus state. The pattern is consistent across the platform.

Keyboard navigation

Every interaction is available without a mouse. Tab order is logical. Skip links are present where needed.

Screen reader support

Interactive components have ARIA labels. Live regions announce dynamic feedback. Tested with VoiceOver and NVDA.

Reduced motion

We honour the prefers-reduced-motion setting. Animations are disabled when set.

Captions and transcripts

Every audio interaction — including learner-to-persona voice scenarios — ships with captions and a transcript.

Touch targets

A 44-by-44-pixel minimum for all tappable elements on mobile.

Multilingual readiness

Font stack includes Noto Sans for multilingual coverage — particularly for AMEP and settlement audiences.

Audit and testing

How we keep the floor in place.

Testing is structural, not occasional. The cadence is documented internally and audit results will be summarised on the research and evidence page once the cadence is established.

  • Automated testing: axe-core or Lighthouse on every deploy.
  • Manual testing: keyboard-only navigation on a defined cadence.
  • Screen reader testing: VoiceOver and NVDA before major releases.
  • Colour-vision simulation: deuteranopia, protanopia, tritanopia.
  • External audit cadence: [to be confirmed — recommend at least annually].

See research and evidence

Reporting an issue

If something doesn't work for you, please tell us.

We'll acknowledge within [SLA — to be confirmed; recommended 2 business days] and work with you on a fix. If the fix takes longer than the acknowledgement, we'll keep you informed.

[email protected]