Motion and Interaction · Labs · 4 min read
Audit a page for reduced motion
A guided lab: list every motion on one page, switch on Reduce motion and walk it again, match each motion to the WCAG criterion that covers it, and write a prioritised fix list. About an hour, with a browser and the system setting.
People switch on Reduce motion because movement on a screen can make them dizzy or sick. Most pages ignore the setting. You'll audit one page the way a person with a vestibular disorder would meet it: with the setting on. Every motion gets a line, a WCAG reference and a verdict, so the fix list is something a team can act on.
What you'll do:
- List every motion on one page and what starts it
- Walk the page again with Reduce motion on
- Match each motion to the WCAG criterion that covers it
- Write a fix list, worst first
You'll need: a browser, the reduced-motion setting of your system, a spreadsheet or paper, about an hour. A page with some motion: a marketing home page usually has plenty.
1. List the motion
Walk the page with the setting off. Load it, scroll it to the bottom, open every menu, hover the cards, click an anchor link. Write a row for each thing that moves, with what moves and what starts it:
- On load: videos, carousels, animated illustrations, badges.
- On scroll: parallax, things that fade or slide in, sticky headers that shrink.
- On interaction: menus, accordions, hovers, smooth scrolling to an anchor.
2. Switch on Reduce motion and walk it again
Turn it on: macOS 26, System Settings › Accessibility › Motion › Reduce motion; Windows 11, Settings › Accessibility › Visual effects › Animation effects (off); iOS, Settings › Accessibility › Motion; Android, Settings › Accessibility › Remove animations (MDN, prefers-reduced-motion). In Chrome DevTools you can also emulate it in the Rendering panel.
Reload and repeat every step. In a new column, write what happens now. "Same as before" is the most common answer, and the reason for this lab.
3. Match each motion to a criterion
Three WCAG 2.2 criteria cover almost everything:
| Criterion | Level | Covers | Passes when |
|---|---|---|---|
| 2.2.2 Pause, Stop, Hide | A | Moving, blinking or scrolling content that starts by itself, lasts more than five seconds and sits next to other content | People can pause, stop or hide it |
| 2.3.1 Three Flashes or Below Threshold | A | Anything that flashes | Nothing flashes more than three times in one second, or the flashes stay under the thresholds |
| 2.3.3 Animation from Interactions | AAA | Motion triggered by an interaction, scrolling included | It can be turned off, unless it's essential |
Two details from the Understanding documents change verdicts. In 2.3.3, colour and opacity changes that don't change size, shape or position aren't motion animation, so a fade passes. And scrolling content into view is essential because the person controls it, but extra effects on top of it, like parallax, aren't. The sufficient technique for 2.3.3 is exactly the media query, technique C39, "Using the CSS prefers-reduced-motion query to prevent motion".
4. Give each row a verdict and a fix
| Motion | Trigger | Criterion | With Reduce motion on | Result | Fix |
|---|---|---|---|---|---|
| Hero video, loops for 20 s | Starts on load | 2.2.2 Pause, Stop, Hide (A) | Still plays; no pause button | Fails A | A visible pause button; under reduce, show the poster frame and don't autoplay |
| Sale badge, flashes red | Starts on load | 2.3.1 Three Flashes or Below Threshold (A) | Flashes 4 times a second | At risk, A: fails if the flash is big or bright enough to pass the thresholds | Don't measure it, remove it: a static badge for everyone |
| Parallax on the hero image | Scroll | 2.3.3 Animation from Interactions (AAA) | Still moves at a different speed | Fails AAA | Under reduce, the image scrolls with the page |
| Smooth scroll to "Reviews" | Click on an anchor link | 2.3.3 Animation from Interactions (AAA) | Still glides down the page | Fails AAA | scroll-behavior: auto under reduce |
| Card hover, lifts 4 px | Hover | 2.3.3 Animation from Interactions (AAA) | Still lifts | Fails AAA (low risk) | Keep the shadow change, drop the lift |
| Menu slides in, 250 ms | Click on "Menu" | 2.3.3 Animation from Interactions (AAA) | Fades in, 150 ms, no slide | Passes | Nothing; note it as the model for the others |
The figure is a finished audit of a product page. For each row write the result (passes, fails, at risk) and one concrete fix. Good fixes are specific:
- "Add a pause button" for a looping video, and under reduced motion, show the poster frame instead of autoplaying.
- "
scroll-behavior: autounder reduce" for smooth scrolling. - "Keep the shadow change, drop the lift" for a hover.
5. Order the fixes
- Level A failures first. They affect everyone, and 2.3.1 can trigger seizures. A flashing element has no reason to stay: remove it rather than measure it.
- Then large movement. Parallax, zooms, full-screen slides and anything that moves the background against the foreground: these are the motions most likely to make people with vestibular disorders unwell (see Vestibular disorders and reduced motion).
- Then small movement on interaction: lifts, slides, bounces.
6. Look at the code
Search the CSS for prefers-reduced-motion. No results means the setting is ignored everywhere. Then look for scroll-behavior: smooth, autoplay and animation-iteration-count: infinite: each is a row you may have missed.
If the product has motion tokens, check that the reduced values exist there, so one fix reaches every component (see Motion tokens).
7. Check your work
Reflection questions: Which motion surprised you most with the setting on? Which fix would you ship first, and what would it cost?
Related
Designing a reduced-motion version · WCAG and motion · Vestibular disorders and reduced motion · Audit the motion in your product · Accessibility fundamentals · Reduced-motion substitution table