# Manual accessibility review checklist Automated axe checks do not establish WCAG conformance. A human reviewer must review every route record in `docs/accessibility/route-reviews/` against one release candidate and sign them. The required scope is the route registry (`ROUTE_REGISTRY` in `src/features/installed-feature-contracts.ts`): one record per route, named `.md`. Copy the template fields exactly; the gate rejects blank identity/timestamp/signature fields, pending verdicts, mismatched release IDs, or missing routes. The signed review is the release gate FE-GATE-028 (`review:a11y-manual`), so it is required once per release candidate, not on every merge. The merge gate FE-GATE-009 runs `review:a11y-manual -- --format-only`: each record must keep the fields below with `pending`, `pass` or `not-applicable ()` verdicts, and a record marked `reviewed` must be complete. This document keeps no route list. A list here once said six routes while ten were registered, and keeping it current made every new feature edit this file. Instead `verify:documentation` fails, naming the route ID, when a registered route has no record file. A new route starts from a copy of a pending record with its title and `Route ID` changed. Allowed item verdicts: - `pass` - `not-applicable ()` Required record: ```text Status: reviewed Route ID: APP_HOME Release ID: Reviewer: Reviewed at: Signature: Attestation: accepted M1 Keyboard: pass M2 Visible focus: pass M3 Route focus: pass M4 Modal focus: not-applicable (no modal on this route) M5 Error association: not-applicable (no form error on this route) M6 Color signal: pass M7 Reduced motion: pass Screen reader: pass Notes: ``` The reviewer must verify: - M1: every action works without a pointing device - M2: every focused element has a visible indicator - M3: route transitions move focus to a deterministic target - M4: modal focus is trapped and restored, when a modal exists - M5: errors are programmatically associated with their controls, when present - M6: state never relies on color alone - M7: non-essential motion is suppressed with reduced-motion preference - Screen reader: headings, live regions, errors, and actions are announced once A route with a form or a dialog requires real M4 modal and M5 field-error review; those items must not be marked not-applicable on that route. Passing automated evidence means only that tested pages had no critical or serious axe findings under the recorded Chromium, Firefox, and WebKit runs. What the automated run scans: - Every registered route, after the route's own `h1` is on screen, so the scan never lands on the app shell's loading surface (`tests/e2e/accessibility.spec.ts`). A public route's `h1` must equal its catalog title. - Protected routes after the demo sign-in, never the sign-in prompt. A list read answers an empty list in the frame its descriptor declares (inside the Envelope for `responseEnvelope: "ENVELOPE_V1"`), and the scan runs only once no alert box is on screen, so a list page is scanned in its empty state. A read of one resource (a detail page) has no generic answer: that route is scanned in its failure state and the run records an `a11y-data-state` annotation. `a11y.json` lists it under `notChecked`. When a protected route's `paramsSchema` is the input of such a read, the report expects that record from the descriptors alone and fails without it (`scripts/write-a11y-report.ts`). - The list of the feature `create:feature` writes, in its success, empty and error states, its detail and its form with submit errors, each after that state is on screen (`tests/e2e/generated-feature.spec.ts`, on a build with that feature). A product's own features get the route scan above.