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.
- 01Open and close every modal or drawer
- 02Trigger validation and route changes
- 03Find removed focused elements and invisible focus
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.
- 01Move focus only when context changes
- 02Trap and restore focus in modal dialogs
- 03Use visible focus styles and status announcements
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 opening, nested action and closing flows
- 02Navigate browser history
- 03Use screen reader and keyboard together
Common pitfall
A shortcut to avoid
Automatically moving focus after every update can be more disorienting than leaving it in place.
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.