Editorial recipe — not benchmarked — reviewed September 1, 2026
Find and fix an accessibility regression
For web teams with representative user flows, browser tests, and access to manual accessibility review.
Run this recipe
Work through it here
Progress stays in this browser. The downloaded Markdown kit works in any notes app or repository.
0/5 complete
Procedure
- Name the affected flow, browser states, and applicable WCAG 2.2 success criteria; preserve a failing example before changing code.
- Add the smallest Playwright and axe-core check that reaches each affected interactive state and records the initial violations without disabling rules.
- Ask Codex to trace the shared component or style causing the failure, implement the root-cause fix, and retain a regression check alongside the existing functional tests.
- Run the functional and accessibility checks, then have Claude Code review the diff for semantic structure, keyboard operation, focus behavior, labels, errors, and unintended regressions.
- Complete manual keyboard and screen-reader checks, add inclusive user testing when consequence warrants it, and record remaining gaps rather than claiming universal conformance.
Acceptance artifact
A reproducible failing case, root-cause fix, passing automated regression check, second-model diff review, and manual-test record
Do not use it blindly
Automated accessibility checks find only some problems; a passing axe run is not WCAG conformance and does not replace manual assessment or feedback from people with disabilities.