Motion and Interaction · Step 6 · 7 min read
Designing a reduced-motion version
A reduced-motion version is a design, not a switch that turns everything off. How to keep what each motion means while dropping the travel, a table of common motions and their reduced versions, two ways to write it in CSS, and how to test it.
Reduced motion means the same message, delivered without the trip. When someone turns on reduce motion, they still need to know the panel opened, the item was saved, the page changed. What they don't need is the panel flying across the screen to tell them. So every animation gets a second design: what does this motion say, and what's the smallest change that still says it?
What you'll be able to do after reading:
- Find the meaning of a motion, separate from its movement
- Choose a reduced version for the common interface motions
- Write it in CSS in one of two ways, and know the trade-off
- Test the reduced version on purpose, not by accident
1. One panel, two designs
translateX(100%) to 0, 300 ms, ease-out. Your device asks for reduced motion, so this side fades too.
ease-out. No travel, the same news.
Both panels say the same thing: a set of filters arrived on top of the page, and the page is still behind it, dimmed. The left one says it with travel, from the edge where the panel lives. The right one says it in place, with a short fade. Nobody who uses the right one is missing information; they're missing 300 ms of sliding. This is the code, both versions in one file:
.mo-c-rp--full .mo-c-rp__panel { transform: translateX(100%); transition: transform 300ms ease-out; }
.mo-c-rp--reduced .mo-c-rp__panel { opacity: 0; transition: opacity 200ms ease-out; }
.mo-c-rp:has(.mo-c-play:checked) .mo-c-rp--full .mo-c-rp__panel { transform: none; }
.mo-c-rp:has(.mo-c-play:checked) .mo-c-rp--reduced .mo-c-rp__panel { opacity: 1; }
@media (prefers-reduced-motion: reduce) {
.mo-c-rp--full .mo-c-rp__panel { transform: none; opacity: 0; transition: opacity 200ms ease-out; }
.mo-c-rp:has(.mo-c-play:checked) .mo-c-rp--full .mo-c-rp__panel { opacity: 1; }
}
In a real product there's one panel, not two: the media query at the end is the whole reduced version. The figure shows both only so you can compare them.
2. Find the meaning first
Before choosing a reduced version, write one sentence about what the motion tells people. The reduced version must still say it.
- "The panel came from the right, so it goes back there." Direction is the meaning. A fade loses it, so keep a tiny slide of a few pixels, or add a close button on the right edge where people will look for it.
- "This item was added to the cart." The meaning is the change in the cart. A badge that fades in with the new number says it with no travel at all.
- "The page is still working." A loader can pulse in opacity instead of spinning across the screen.
- "This is decoration." Then the reduced version is nothing. Remove it.
This is the same thinking as What motion does in an interface: motion that has a job keeps the job; motion that has none goes first.
3. Common motions and their reduced versions
| Motion | What it means | Reduced version |
|---|---|---|
| Panel or sheet slides in | Something arrived, from that edge | Fade in place, 150 to 200 ms |
| Page or screen slides sideways | You went forward or back | Crossfade, or an instant swap |
| Shared element flies to its new place | This is the same thing, bigger | Crossfade; the element appears in its new place |
| Card zooms to full screen | You opened this card | Crossfade to the full view |
| Parallax backgrounds | Depth, atmosphere | Static background |
| Content flies in on scroll | Not much: it was there already | Visible from the start |
| Carousel advances by itself | More items exist | Static first item, with manual controls |
| Smooth scroll to an anchor | You jumped to this section | Instant jump (scroll-behavior: auto) |
| Spinner | Still working | Opacity pulse, or a progress bar or text |
| Button lifts on hover | You can press this | Colour change only |
| Autoplaying background video | Mood | A still poster, with a play button |
None of these is a rule. They're starting points for your own list, which belongs in your motion documentation (see Documenting motion in a design system).
4. Two ways to write it
C39, W3C's technique for 2.3.3, shows both (W3C, C39).
Override. Write the motion, then undo it inside @media (prefers-reduced-motion: reduce). That's what the panel above does. It's easy to add to existing code, but it's also easy to forget one rule, and the motion leaks through.
Opt in. Write the still version first, and add motion only inside @media (prefers-reduced-motion: no-preference). The ticker in WCAG and motion and the shared element in Web Animations and View Transitions work this way. Anything you forget simply doesn't move, which is the safe failure. It's the better default for new components.
A third pattern you'll see online sets every animation and transition duration to nearly zero for the whole page when reduce is on. It's a quick safety net for an old codebase, but it's blunt: it removes fades and feedback people still need, and it can break code that waits for an animation to end. Use it as a stopgap, never as the design.
5. More than the media query
- Offer a control on the page when your product has a lot of motion. W3C lists a site-wide setting to turn off non-essential animation as a way to meet 2.3.3, for people who never found the system setting (W3C, Understanding 2.3.3).
- Check JavaScript-driven motion too. CSS media queries don't stop animations started by code, Lottie players or videos. The code has to read the same preference and choose.
- Keep timing for meaning. A toast that disappears after a few seconds still disappears with reduce on; it just fades instead of sliding.
6. Test it on purpose
- Emulate it. In Chrome DevTools, open Rendering and set "Emulate CSS media feature prefers-reduced-motion" to
reduce(Chrome for Developers, Emulate CSS media features). - Use it for real. Turn on the system setting on a phone and use the product for a task, not a tour.
- Check every motion in your list from section 3: does each one still say what it means?
- Look for leaks: carousels, videos, Lottie files, scroll effects and third-party widgets are the usual suspects.
The lab Audit a page for reduced motion walks you through this on a real page.
7. Common mistakes
- Turning every animation off, including feedback people need.
- A reduced version that's just the full one, faster.
- Forgetting motion started by JavaScript, Lottie or video.
- Writing the reduced version after launch, as a ticket nobody picks up.
- Testing it only in the emulator, never with the real setting on a phone.
8. Vocabulary
| Term | Meaning |
|---|---|
| Reduced-motion version | The design of a motion for people who asked for less: same meaning, no large travel |
| Override | Writing motion first, then undoing it for reduce |
| Opt in | Writing the still version first, then adding motion for no-preference |
| Crossfade | One state fading out while the next fades in |
| Leak | Motion that still runs with reduce on, because something forgot to check |
9. Try it (no tools needed)
- Pick five motions in a product you know.
- For each, write the one-sentence meaning.
- Next to it, write the reduced version that keeps that meaning. If you can't find a meaning, write "remove".
Reflection questions: How many of the five ended up as "remove"? Would the product be worse for everyone without them, or better?
10. If you already practise
- Add a "reduced version" field to every motion spec and every motion token (see Motion tokens).
- Write new components opt-in: still first, motion inside
no-preference. - Keep a list of your product's motions and their reduced versions, and review it in critique (see Reviewing motion in critique).
- Ship an on-page motion control if your product is motion-heavy.
Checklist
Learn more
- W3C: C39, Using the CSS prefers-reduced-motion query · Understanding 2.3.3, Animation from Interactions
- MDN, prefers-reduced-motion
- Chrome for Developers, Emulate CSS media features
- Val Head, Designing Safer Web Animation For Motion Sensitivity (A List Apart, 2015)
- James Craig, Responsive Design for Motion (WebKit, 2017)
Books, courses and videos to go deeper
- Accessibility for EveryoneLaura KalbagBook · A Book Apart, 2017 (Amazon)
- Designing Interface AnimationVal HeadBook · Rosenfeld Media, 2016 (Amazon)
Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.
Related
Vestibular disorders and reduced motion · WCAG and motion · CSS transitions and animations · Audit a page for reduced motion · Motion tokens · Reduced-motion substitution table