17 lines
838 B
Markdown
17 lines
838 B
Markdown
# Browser Journey and Accessibility Tests
|
|
|
|
Browser tests MUST run against a disposable local or appliance target, never a production customer.
|
|
|
|
Required coverage:
|
|
|
|
- supported desktop browser viewport plus 200% zoom/reflow;
|
|
- keyboard-only primary and failure/recovery journeys;
|
|
- visible focus, logical order, accessible names, headings and landmarks;
|
|
- dynamic status, progress, validation and completion announcements;
|
|
- loading, empty, ready, degraded, failed, restricted, unavailable and stale states;
|
|
- 1-second navigation feedback and 2-second operation acknowledgement trials;
|
|
- screenshots and machine-readable results stored outside source control.
|
|
|
|
The final browser runner and dependency versions MUST be pinned when implementation selects them.
|
|
Automated accessibility results never replace the manual WCAG 2.2 AA checklist.
|