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 transitions, auto-play and parallax
- 02Identify animations longer than the underlying work
- 03Check reduced-motion behavior
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 motion by functional purpose
- 02Keep durations proportional and interruptible
- 03Provide reduced or removed alternatives
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.
- 01Enable prefers-reduced-motion
- 02Test keyboard and rapid navigation
- 03Profile animation smoothness on modest devices
Common pitfall
A shortcut to avoid
Shortening every animation does not fix movement that has no explanatory role or interrupts the task itself.
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.