Evidence review
What to inspect before changing anything
Start with the delivered website and the real user journey. Record the current state so the team can distinguish an observed problem from an assumption and compare the same surface after deployment.
- 01Run automated checks on representative states
- 02Complete tasks by keyboard
- 03Review names, headings, errors and contrast
Implementation
A practical improvement plan
Make the smallest coherent change that solves the observed problem. Keep normal code review, accessibility, security and product checks in the loop instead of optimizing for the scan alone.
- 01Fix blockers in native semantics and focus
- 02Provide text alternatives and perceivable status
- 03Document complex widget behavior
Verification
How to verify the result
Verification should test the intended outcome and the most likely regression. Use the production delivery path whenever headers, caching, rendering or third-party services affect the result.
- 01Test with assistive technology
- 02Repeat at 200 percent zoom and narrow widths
- 03Retest after every blocking fix
Common pitfall
A shortcut to avoid
Passing an automated checker covers only a subset of barriers and should not be presented as accessibility certification.
Further reading
Primary guidance and references
These sources provide standards, security guidance or the interpretation framework used to keep this guide bounded. Product-specific implementation still requires review in the actual codebase.