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>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
861383283c
commit
f17572a4be
@@ -63,3 +63,16 @@ The reviewer must verify:
|
||||
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).
|
||||
|
||||
Reference in New Issue
Block a user