Skip to content

M9-09 Accessibility (WCAG 2.1 AA) Compliance Pass

Milestone: M9 — Hardening and Compliance SOW Reference: NFR2 (and NFR1's "user interfaces must be mobile-responsive") Requirement Clarity: ✅ Clear Dev Status: ❌ Not started — only incidental aria-label attributes exist from MUI defaults; no systematic audit or tooling

Overview

Bring the platform's web interfaces up to WCAG 2.1 AA compliance so users with disabilities can complete registration and other core tasks without barriers.

Backend Tasks

  • N/A

Frontend Tasks

  • Add accessibility testing tooling (axe-core / jest-axe) to the test suite
  • Run an accessibility audit across all key screens (issuing, disclosure, verification, admin)
  • Fix keyboard navigation, screen-reader compatibility, and colour-contrast issues found
  • Verify responsive/mobile-friendly behaviour across the same screens

Dependencies

  • Should ideally run continuously as M2/M3/M5/M7 UI is built, not only as a one-off pass at M9 — flag this to the team early.

Acceptance Criteria

  • WCAG 2.1 AA compliance assessment completed
  • Keyboard navigation verified
  • Screen reader compatibility verified
  • Colour contrast checks passed (per SOW Appendix 3, Accessibility)

Existing Reference Material

None — no accessibility work has started.

Blockers & Risks

  • Risk: deferring all accessibility work to M9 risks discovering structural issues (e.g. non-semantic markup) too late to fix cheaply — recommend an early spot-check during M2/M3.