# Use motion to explain continuity

ID: cmp-motion-continuity. Sources: [S25](https://developer.mozilla.org/en-US/docs/Web/API/View_Transition_API), [S26](https://developer.mozilla.org/en-US/docs/Web/CSS/Guides/Scroll-driven_animations), [S23](https://www.w3.org/WAI/WCAG22/Understanding/animation-from-interactions.html).

Teach motion that explains a state change, progression, or relationship. Design the static experience first. Use consistent movement character where motion has a purpose.

Application A: a project thumbnail transitions into its detail context. Application B: a process explanation highlights the current relationship while essential text stays available.

Counterexample: parallax delays access to service scope, or a failed reveal keeps proof invisible.

Mobile: preserve normal scrolling, reduced motion, static fallback, and focus. Verify specific feature support, interruption, and repeated navigation. Do not add effects solely to diversify output.

Storyboard: state purpose, change, fallback, and expected observation. Review: execute motion states and inspect reduced-motion/no-enhancement behavior as well as stable captures.

## Authority and use

This is an original design-teaching hypothesis. It is advisory and does not change factual, accessibility, or functional requirements. Adapt it to verified business evidence and inspect the current render before accepting an outcome. The applications above are contrasting examples, not copyable site presets.