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.
- 01Count primary-looking actions per view
- 02Compare link, secondary and destructive styles
- 03Inspect loading, disabled and focus states
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.
- 01Allow one primary action per decision area
- 02Use labels that describe the outcome
- 03Define complete interaction states
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.
- 01Navigate with keyboard and screen reader
- 02Test double submission and loading transitions
- 03Ask users which action they expect to take
Common pitfall
A shortcut to avoid
Turning every secondary action into a low-contrast text link can hide important choices.
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.