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.
- 01Audit repeated components and brand attributes
- 02Separate borrowed defaults from intentional conventions
- 03Find where product meaning could shape the system
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 a few high-signal brand decisions
- 02Keep common controls behaviorally familiar
- 03Document when and why variants exist
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.
- 01Apply the system to unrelated page types
- 02Run usability checks on unusual treatments
- 03Review whether the product is recognizable without the logo
Common pitfall
A shortcut to avoid
Making every component unconventional creates friction and maintenance cost rather than a coherent identity.
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.