소유자 결정(2026-11-07, design-docs repo-structure/README.md 3.4절)으로 템플릿 샘플을 지운다. 샘플이 맡던 시험 대상은 앞 커밋들이 옮겼다. 참조 기능과 예제 화면, 두 context, 그 시험, e2e 3개, 수동 접근성 기록 7개, 런타임 프로필 키, test:reference-feature(명령, 산출물, 게이트 참조), 커버리지 정책 행을 지웠다. removable-template-features 목록은 비우고 장치는 남겼다: test:sample-removal은 인자가 없으면 목록을 하나씩 지우고, 비면 SKIP을 출력하고 보고서에 건너뛴 사례를 남긴다. 기능 스위치 시험과 홈 시작 링크 스위치 시험은 시험 전용 fixture 기능으로 옮겼다. browser soak은 생성 기능을 넣은 빌드에서 돈다. 문서의 샘플 경로를 고쳤다. 날짜가 붙은 설계·리뷰 기록의 본문은 그대로 두었다. 레지스트리 기준선(update:registry-baseline, OWNER DongHyeonka), CI 계약 기준선과 workflow, 초기 JS 기록(194,354B, 17파일, 첫 기능 6,327B, 기능 539B, context 4B)을 다시 받았다. 위험: 레지스트리 행 삭제는 breaking이다. 샘플을 고쳐 쓰는 다운스트림은 수정/삭제 충돌을 만난다. 성능 lab의 기능 라우트 측정은 템플릿에 공개 기능 라우트가 없어 measured:false다. TEMPLATE_FIXTURE 출처는 플랫폼 코드에 남았다. 검증(desktop): check:types, lint, check:architecture, check:registries, check:ci, verify:documentation, test:unit, test:component, test:contract, test:integration, test:recipes, test:coverage(Risk coverage PASS 378/378, 문턱 68개), test:e2e 183, test:a11y, test:visual, test:storybook, test:browser-capabilities, test:feature-scaffold PASS(76 checks), test:sample-removal SKIP, build, check:bundle.
85 lines
3.9 KiB
Markdown
85 lines
3.9 KiB
Markdown
# 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:
|
|
|
|
```text
|
|
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
|
|
|
|
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.
|