Files
tech-log-frontend/docs/accessibility/manual-checklist.md
T
DongHyeonka c80320dfc7 chore: sync the frontend template from ebea300 to af3d8e6
Carries 359 template commits, tag v0.2.0 plus one documentation commit: the
generator-built feature index with its app, bounded-context and feature
declarations, the src/platform kernel and scale tooling, the 2026-09-24 src
review fixes, and the 2026-09-25 maturity review round with its CHANGELOG
[보안]/[계약] rows. 691 of the 824 template paths are applied, 85 of them
merged with product changes; 127 are not carried.

Product identity is unchanged: name, version 0.1.0, routes, design and the
TechLog domain.

Three decisions worth naming. TechLog stays composed directly, as the last
two syncs recorded; its directory carries a NOT_INSTALLED marker that says so,
and every installed-* composer takes the template's projection with TechLog
added on top. The reference sample is no longer installed: the template now
installs a feature only through feature-module.ts and context-routes.ts,
which load the screens this product deleted, so its three operations, six
schemas and one topic leave the registries, recorded as registry change
evidence. And AppRouter mounts the platform and TechLog routes only; the
template's bounded-context route gateway waits for a generator-installed
feature.

Required fixes: readSubject on the BFF session owner (without it every HTTP
Studio session would close as integration-failed), zod through the facade in
nine TechLog files, noUnusedLocals, and public/config.json written out to
match the local profile. Derived baselines were recomputed after reproducing
both sides' values: CI contract 101 commands / 106 references / 141
artifacts, gate shape c9adcf85; registry approval 2dc6c3a3; the runtime
config schema baseline equals the schema at 8210d48.

Verified here: types, lint, architecture, adapter inventory, CI contract,
i18n, design system, diagnostics, browser security, dev release manifest,
TechLog contract and build pass; 220 component, 155 integration, 15
contract, 418 TechLog, 43 reference-feature, 18 recipe and 46
release-coherence tests pass, and 2381 of 2383 unit tests. Reproduced at
8210d48 first and unchanged: check:registries (byte-identical),
test:runtime-schema, verify:documentation. Brought by the template and
escalated rather than suppressed: check:request-fanout on TechLog's cursor
pagination, check:remediation-ledger (fails upstream too), the shared-chunk
hash test, and the registry-dependent sample removal and second-feature
tests. Playwright suites were not run.

Full record, the five open questions and the follow-ups in
docs/operations/template-sync-2026-09-29.md.

(cherry picked from commit b2170cf265dea45dc9cc05d3c61e627e97f31cdb)
2026-11-12 08:28:54 +09:00

3.2 KiB

Manual accessibility review checklist

Automated axe checks do not establish WCAG conformance. A human reviewer must review all 27 route records in artifacts/tests/a11y-manual/ against one release candidate and sign them. The required TechLog Public and Studio scope is derived from the installed route registry, so the gate rejects stale, missing, or additional route records as well as blank identity/timestamp/signature fields, pending verdicts, and mismatched release IDs. The scope is: NOT_FOUND, TECH_LOG_CASE, TECH_LOG_EXPLORE, TECH_LOG_EXPLORE_KIND, TECH_LOG_HOME, TECH_LOG_PROFILE, TECH_LOG_PROJECT, TECH_LOG_PROJECTS, TECH_LOG_PROJECT_ACTIVITY, TECH_LOG_PROJECT_DECISIONS, TECH_LOG_PROJECT_RECORDS, TECH_LOG_QUESTION, TECH_LOG_REFERENCE, TECH_LOG_RELEASE, TECH_LOG_RELEASES, TECH_LOG_SEARCH, TECH_LOG_STUDIO_DOCUMENTS, TECH_LOG_STUDIO_DOCUMENT_EDIT, TECH_LOG_STUDIO_DOCUMENT_NEW, TECH_LOG_STUDIO_DOCUMENT_PREVIEW, TECH_LOG_STUDIO_DOCUMENT_PUBLISH, TECH_LOG_STUDIO_DOCUMENT_VALIDATION, TECH_LOG_STUDIO_HOME, TECH_LOG_STUDIO_NOT_FOUND, TECH_LOG_STUDIO_PUBLICATIONS, TECH_LOG_STUDIO_PUBLICATION_PREVIEW, TECH_LOG_TOPIC.

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. The template carried the same rule for its own example screens; the route set is this product's, the rule is the template's.

Allowed item verdicts:

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

Required record:

Status: reviewed
Route ID: <exact installed route ID>
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

Routes with dialogs or form errors require real M4 modal-focus or M5 error-association review; those items must not be marked not-applicable when the reviewed route exposes the relevant behavior. Passing automated evidence means only that tested pages had no critical or serious axe findings under the recorded browser runs.