# Reduced Motion

Reduced motion design removes or substitutes nonessential movement when users request less animation through system or product preferences.

- Type: practice
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/reduced-motion/>)

## What it means

Reduced motion is an accessibility response to motion that may distract, disorient, or trigger vestibular symptoms. On the web, the prefers-reduced-motion media feature can detect a platform preference; products may also offer their own control when appropriate.

## Why it matters

Large movement, parallax, zooming, spinning, and unexpected transitions can make a product uncomfortable or unusable. Respecting preferences lets teams retain necessary state feedback while avoiding decorative or spatial motion that imposes a cost on some users.

## When to use it

Plan reduced-motion behavior whenever a product uses animated transitions, auto-moving content, scrolling effects, data movement, celebration effects, or interaction-triggered animation. Define alternatives before animation becomes embedded in component APIs.

## How it works

1. Classify motion as essential to understanding, useful feedback, or decorative.
2. Use the platform preference as a default signal and provide a product control when warranted.
3. Remove decorative movement and replace spatial transitions with instant changes or subtle fades.
4. Keep essential feedback perceivable without requiring users to track movement.
5. Pause, stop, or hide automatically moving content where relevant.
6. Test the preference across components, route transitions, canvas content, and third-party embeds.

## A practical example

A project board normally slides a card across columns after a move. With reduced motion enabled, the card appears immediately in its new location, a brief static highlight marks the destination, and a status message confirms the change without a sweeping transition.

## Where it breaks

Reduced motion does not always mean removing every transition; abrupt changes can also be confusing, and some animation may be essential to the task. The platform preference is not a diagnosis, browser and embedded-content support varies, and third-party motion may need separate controls.

## Common mistakes

- Shortening a dramatic animation while preserving the same large movement.
- Disabling CSS animation but forgetting JavaScript, canvas, GIF, or video motion.
- Removing motion without preserving state-change feedback.
- Treating prefers-reduced-motion as the only control users may need.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/reduced-motion/#visualization-reduced-motion>)

## Sources

1. [Understanding Success Criterion 2.3.3: Animation from Interactions](<https://www.w3.org/WAI/WCAG22/Understanding/animation-from-interactions>) — W3C Web Accessibility Initiative · Standards guidance
2. [Web Content Accessibility Guidelines \(WCAG\) 2.2](<https://www.w3.org/TR/WCAG22/>) — World Wide Web Consortium · Standard
3. [Making your service accessible: an introduction](<https://www.gov.uk/service-manual/helping-people-to-use-your-service/making-your-service-accessible-an-introduction>) — Government Digital Service · Government guidance

## Related topics

- [Motion Design](<https://wiki.soroush.uk/topic/motion-design/>)
- [Accessibility](<https://wiki.soroush.uk/topic/accessibility/>)
- [Component Library](<https://wiki.soroush.uk/topic/component-library/>)
