Browser, Responsive, and Accessibility Tests
How browser navigation, interaction, keyboard, and a11y checks protect documentation and clients.
Run desktop/mobile navigation smoke tests and axe-backed checks on changed surfaces.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
The documentation repository uses Playwright foundation coverage and accessibility checks. The source application also exposes admin E2E, keyboard, RBAC, performance, and visual scripts.
| Check | Source-backed expectation |
|---|---|
| Scope | A passing desktop smoke test does not prove responsive or keyboard completeness. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | pnpm test:e2e && pnpm test:a11y |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
pnpm test:e2e && pnpm test:a11y
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.