Accessibility
Accessibility reference for the Vetrix web surface: how a release is verified by hand against assistive technology, and how that verification is held in place automatically by CI. The manual page is the reviewer's script; the gating page is the operator's spec for the checks that block a merge. Read them together — the gate catches machine-detectable regressions only, and the manual walkthroughs cover the behaviour axe and pa11y cannot see.
Pages
- Manual verification procedures — Executable walkthrough scripts for the three mandatory screen-reader matrices (NVDA + Firefox ESR on Windows, VoiceOver + Safari on macOS, Orca + Firefox ESR on Ubuntu), each naming the keystroke, the expected utterance, and the fail condition per page — login, repository browse, issue detail, merge-request review, board, pipeline log, and the admin user list — plus procedures for 400% page zoom and 200% text-only zoom, reduced motion and forced colour schemes, Chrome DevTools colour-blindness emulation against every status badge, a keyboard-only baseline pass with focus-trap checks, and the reporting and pre-release sign-off checklists.
- Accessibility regression gating — Operator spec for the
three moving parts of the gate: the branch-protection configuration that makes
the axe/pa11y and Playwright a11y contexts required checks on
developandmaster(including the sibling skip job that must still report a context on merge requests that do not touchweb/, or the evaluator refuses the merge), the nightly full-route axe run and the script that files a bug ticket when it fails, and the triage runbook and ordered rollout — land each emitting job before applying the protection rule, otherwise nothing can merge.