Files
clean-architecture-frontend…/docs/accessibility/manual-checklist.md
T
DongHyeonka fbd8f7d148 chore(review): 1103 게이트·드릴 조치 브랜치를 합친다
Refs: docs/reviews/2026-11-03-maturity-review/README.md 02-06 11-06 12-09 10-01 11-03~11-05 12-02 12-04 12-05 12-08 14-04 16-02

# Conflicts:
#	docs/manual/01-add-a-feature.md
#	docs/manual/02-decision-tables.md
#	docs/manual/reference/patterns.md
2026-11-04 23:08:05 +09:00

3.5 KiB

Manual accessibility review checklist

Automated axe checks do not establish WCAG conformance. A human reviewer must review every route record in artifacts/tests/a11y-manual/ 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 <ROUTE_ID>.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 (<reason>) 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 (<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. 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.
  • 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).