Files
clean-architecture-frontend…/docs/accessibility/manual-checklist.md
T
DongHyeonkaandClaude Opus 5.5 f17572a4be test(a11y): scan the rendered route, signed in and per state (08-05, 11-02)
axe ran as soon as `main` showed, which is the app shell's loading surface,
and protected routes were scanned on the sign-in prompt. The specs now wait
for the route's h1, sign in first, and scan the reference list, detail, form
and status states. The state-surfaces baseline was the loading surface.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-26 00:25:46 +09:00

3.3 KiB

Manual accessibility review checklist

Automated axe checks do not establish WCAG conformance. A human reviewer must review all ten route records in artifacts/tests/a11y-manual/ against one release candidate and sign them. The required scope is derived from the route registry: APP_HOME, EXAMPLES_PLATFORM, EXAMPLES_UI, EXAMPLES_STATES, EXAMPLES_AUTH, NOT_FOUND, REFERENCE_RESOURCE_LIST, REFERENCE_RESOURCE_DETAIL, REFERENCE_RESOURCE_FORM and REFERENCE_RESOURCE_STATUS. 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 (<reason>) verdicts, and a record marked reviewed must be complete.

This list is not maintained by hand: verify:documentation compares it against the installed route registry and fails when a registered route is absent. It said six routes while ten were registered, which put the platform overview and the three reference-resource screens outside the declared manual review scope without anyone deciding they should be.

Allowed item verdicts:

  • pass
  • not-applicable (<specific reason>)

Required record:

Status: reviewed
Route ID: APP_HOME
Release ID: <immutable release ID>
Reviewer: <human reviewer identity>
Reviewed at: <RFC 3339 timestamp>
Signature: <reviewer identity or approved signature reference>
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: <observations and linked defect IDs>

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

EXAMPLES_UI 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. Their API calls answer an empty list there.
  • The reference sample's list in its success, empty and error states, its detail, its form with submit errors and its status page, each after that state is on screen (tests/e2e/reference-form.spec.ts, removed with the sample).