Framework · Motion & interaction · 4 min read
Reduced-motion substitution table
A table that lists every motion in a product with what it means and what replaces it when someone asks for reduced motion (keep, swap or remove), so the reduced version is designed once and keeps the meaning instead of switching everything off.
The movement is the meaning and it doesn't travel far.
A badge number changesLarge travel becomes a fade, a crossfade or an instant change.
Panel fades in placeIt tells people nothing, so the reduced version is nothing.
Parallax becomes a still photoMotion + meaning (one sentence) → keep, swap or remove → same meaning, less travel
Use it when
- Your product honours
prefers-reduced-motionwith one blunt rule that turns every animation off, feedback included. - A team adds a new motion and nobody knows what its reduced version should be.
- You prepare a motion audit, or the motion page of your design system.
How to use it
- List every motion. Walk the product and note each one: panels, page transitions, loaders, scroll effects, carousels, videos, Lottie files, hover lifts. Include motion started by JavaScript and third-party widgets. Output: a list of motions, with where they appear.
- Write the meaning in one sentence. For each: what does it tell people? "Something arrived from the right." "You went one step deeper." "It's still working." "Nothing: decoration." Output: one meaning per row.
- Choose keep, swap or remove. Keep a small, essential motion when the movement is the meaning and it doesn't travel far. Swap large travel for a fade, a crossfade or an instant change. Remove what has no meaning. Output: a decision and the substitute per row.
- Set the timing of the substitute. Fades stay short, around 150 to 200 ms. Anything that disappears on a timer still disappears; it just fades instead of sliding. Output: a duration per substitute.
- Write it opt-in for new components. Build the still version first and add motion only inside
@media (prefers-reduced-motion: no-preference), so anything you forget simply doesn't move. Make JavaScript, Lottie and video read the same preference. Output: the table in the design system, and a code rule. - Test with the real setting. Emulate
reducein the browser, then turn the system setting on a phone and do a real task. Check every row and look for leaks. Output: a pass or a leak per row.
Worked example
The task app for small teams lists its motions while preparing a reduced-motion version:
| Motion | Meaning | Decision | Reduced version |
|---|---|---|---|
| Filter panel slides in from the right | Filters arrived, from that edge | Swap | Fades in place in 200 ms; the close button stays on the right edge |
| Switching boards slides the page sideways | You went to the next board | Swap | Crossfade |
| A task card zooms to full screen | You opened this task | Swap | Crossfade to the full view |
| Spinner while the board loads | Still working | Swap | Opacity pulse and the text "Loading tasks" |
| Parallax illustration on the sign-up page | Atmosphere | Remove | Static illustration |
| Template carousel advances by itself | More templates exist | Swap | First item still, with previous and next buttons |
| "3 new" badge on a board pops | The board has new tasks | Keep, smaller | Number changes with a fade, no scale |
Two rows needed a design decision, not a code change: the filter panel kept its close button on the right so the direction wasn't lost, and the carousel got visible buttons it never had.
Watch out for
- Turning everything off. Feedback and state changes are information. Remove travel, not meaning.
- The same motion, only faster. A slide at 100 ms still slides. Change the kind of motion, not just its speed.
- Leaks. Media queries don't stop motion started by code, Lottie players, videos or third-party widgets. Check them by name.
- A table nobody owns. If new motions don't get a row before release, the reduced version falls behind. Make the row part of the motion spec.
Template
Copy this table into your motion documentation and add a row for every new motion.
| Motion | Where | Meaning (one sentence) | Keep / Swap / Remove | Reduced version | Duration | Tested on |
|--------|-------|------------------------|----------------------|-----------------|----------|-----------|
| ... | ... | ... | ... | ... | ... ms | ... |
Code rule: new components write the still version first and add motion
inside @media (prefers-reduced-motion: no-preference).
JavaScript / Lottie / video: read the same preference before playing.
- Accessibility for EveryoneLaura KalbagBook · 2017 (Amazon)
- Designing Interface AnimationVal HeadBook · 2016 (Amazon)
- C39: Using the CSS prefers-reduced-motion queryW3C (external site)
- Understanding 2.3.3 Animation from InteractionsW3C (external site)
- Emulate CSS media featuresChrome for Developers (external site)
"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.