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.
- 01Read the score band and evidence breadth
- 02Review the strongest raising and lowering drivers
- 03Separate observed findings from model explanation
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.
- 01Prioritize concrete quality findings first
- 02Use score drivers for a design and engineering review
- 03Rescan only after meaningful public changes
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.
- 01Compare the same canonical URL
- 02Confirm evidence breadth is comparable
- 03Record which release and changes were measured
Common pitfall
A shortcut to avoid
Treating the score as a defect percentage invents precision and can produce unnecessary remediation work.
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.