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.
- 01Trace labels, instructions, validation and completion
- 02Check autocomplete and input types
- 03Review long, optional and sensitive fields
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.
- 01Group fields by user task
- 02Validate at a helpful moment without blocking exploration
- 03Connect errors to fields and a summary
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.
- 01Complete the form by keyboard and screen reader
- 02Test invalid, interrupted and duplicate submissions
- 03Verify browser autofill behavior
Common pitfall
A shortcut to avoid
Aggressive live validation can show errors before users have had a chance to finish typing.
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.