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.
- 01Collect errors from validation, network and server paths
- 02Review technical language and missing actions
- 03Check whether entered data survives
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.
- 01Use specific titles and recovery instructions
- 02Preserve valid user work
- 03Provide a request identifier for support when useful
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.
- 01Trigger failures at every workflow stage
- 02Test retry, back and duplicate actions
- 03Read errors with assistive technology
Common pitfall
A shortcut to avoid
Replacing technical details with a generic 'something went wrong' message removes both risk and useful recovery information.
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.