smukh Accessibility regression test
Protect the user-facing behavior that failed, after the repair has been verified in the original state.
Workflow
- Read the before evidence and verified after evidence. State the barrier in terms of user behavior.
- Choose the narrowest reliable layer with references/test-selection.md.
- Make the test fail against the known broken behavior when practical, then pass with the repair.
- Assert outcomes such as focus destination, exposed error, accessible name, or absence of the original fingerprint. Do not assert only that an attribute string exists.
- Control route, state, viewport, reduced motion, and data so the test is repeatable.
- Keep manual-only outcomes as an explicit review record rather than a misleading automated test.
Boundaries
Do not snapshot raw axe output, browser versions, run IDs, or timestamps. Do not weaken a rule, baseline away a new issue, hide content, or remove functionality to make a test pass. A regression test protects its scoped behavior; it does not certify the component or page.