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.
- 01Inventory fonts, sizes, weights and line heights
- 02Measure paragraph line length
- 03Find visually identical roles with different styles
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.
- 01Define display, heading, body and utility roles
- 02Use fluid sizes within safe limits
- 03Set readable measure and consistent vertical rhythm
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.
- 01Review representative pages at 200 percent zoom
- 02Test font loading and fallback behavior
- 03Check long titles and localization-like text expansion
Common pitfall
A shortcut to avoid
Adding more typefaces or weights can disguise inconsistency while increasing load and maintenance cost.
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.