WCAG Launch Accessibility Audit

Last updated: 2026-06-02

Purpose

task-0597 adds a repeatable WCAG 2.1 AA launch audit for the eight launch-critical route entrypoints: dashboard, cases, case detail, documents, calendar, communications, billing, and portal dashboard.

The audit covers:

• Keyboard navigation.
• Focus management.
• Screen reader semantics.
• Contrast and color independence.
• Reduced motion.
• Icon and image alternative text.

Command

npm run launch:accessibility-audit

The command writes:

• planning/wcag-2-1-aa-accessibility-audit.json
• planning/WCAG_2_1_AA_ACCESSIBILITY_AUDIT.md

Failure Mode

By default the command reports findings without failing, because launch acceptance still needs human review and browser proof. To use it as a stricter CI gate:

npm run launch:accessibility-audit -- --fail-on high

Supported values are critical, high, medium, low, and none.

Scope

This is a deterministic source audit. It is intentionally scoped to committed launch route entrypoint files so generated planning evidence is not distorted by unrelated local worktree edits.

Operating Rules

• Treat critical/high findings as launch blockers unless the issue is remediated or explicitly dispositioned.
• Treat medium findings as required browser-proof items before launch acceptance.
• Treat low findings as guardrails for the next UI consistency and accessibility pass.
• Re-run this after route, dashboard, case workspace, billing, communications, document, or portal UI changes.
• Pair this with authenticated Playwright, axe-style runtime checks, screen-reader smoke, keyboard tab-order proof, and computed color contrast sampling before calling launch accessibility complete.