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.
- 01Review critical screens and edge states
- 02Compare system tokens and component variants
- 03Test mobile, zoom and long content
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 broken hierarchy and interaction first
- 02Remove unsupported decorative repetition
- 03Document intentional exceptions
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.
- 01Run task-based reviews with target users
- 02Capture responsive screenshots systematically
- 03Recheck after content and code freeze
Common pitfall
A shortcut to avoid
Late pixel polishing can consume launch time while navigation, comprehension and recovery remain unresolved.
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.