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.
- 01List radius values by component type
- 02Find nested rounded surfaces that create visual noise
- 03Compare controls, cards and modal corners
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.
- 01Choose radius families for controls and containers
- 02Reduce nesting and clipped layers
- 03Use shape contrast only where it has meaning
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 small controls and large panels together
- 02Test focus rings near clipped corners
- 03Check touch targets at mobile sizes
Common pitfall
A shortcut to avoid
Setting every component to the same radius creates consistency at the cost of hierarchy.
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.