Lorixen.
EN

prefers-reduced-motion: respecting the reduce-motion setting

Short answer: Phones and computers have a "reduce motion" setting, and browsers pass it to your site through the prefers-reduced-motion media query. Audit every moving element on your site, then use that query to remove decorative motion (parallax, zooms, background video, auto-advancing carousels) and soften functional motion to simple fades. Test by switching the setting on in your own device and walking through the site.

Animations can make a site feel polished. For some visitors they cause real discomfort: MDN notes that motion such as scaling or panning large objects can trigger symptoms for people with vestibular motion disorders. The good news is that respecting the setting is mostly CSS work, and it rarely makes the site worse for anyone.

Step 1: Understand what the setting does

When someone turns on "reduce motion", they are telling every app and website that they want less non-essential movement. MDN's reference for the media feature describes two values:

  • no-preference: no preference has been set (evaluates as false)
  • reduce: the visitor has turned the setting on (evaluates as true)

Where people find the setting, per MDN as of November 2026:

Device Path
Windows 11 Settings > Accessibility > Visual Effects > Animation Effects
macOS Tahoe and later System Settings > Accessibility > Motion > Reduce motion
macOS 15 and earlier System Settings > Accessibility > Display > Reduce motion
iOS Settings > Accessibility > Motion
Android 9+ Settings > Accessibility > Remove animations

Menu names move between releases, so check your device if a path doesn't match.

Step 2: Audit every moving thing

Open your site and list everything that moves, without your own judgement filtering it yet. Then decide, element by element, whether motion should be removed, reduced or kept.

Element Purpose Reduced-motion treatment
Parallax background on hero Decorative Remove: background stays fixed
Background video in header Decorative Show a still poster image; offer a play button
Auto-advancing carousel Decorative/promotional Stop auto-advance; keep manual arrows
Elements sliding in on scroll Decorative Remove: content is simply visible
Page transitions (slide/zoom) Orientation Replace with a short crossfade or none
Menu drawer opening Functional Keep, but use a quick fade instead of a long slide
Loading spinner Functional Keep, perhaps slower; it signals progress
Hover zoom on product images Decorative Remove scaling; use a border or shadow change
Animated counters ("1,000 customers") Decorative Show the final number immediately
Smooth scroll to anchors Convenience Jump directly

The web.dev article on the media query groups animations by role, singling out decorative effects such as parallax scrolling, background videos and animated gradients as the ones some users find distracting or nauseating. Those are your first cuts.

Step 3: Write the CSS

There are two common patterns. Pick one and use it consistently.

Pattern A: add motion only for people who are fine with it

.hero-card {
  opacity: 1;
}

@media (prefers-reduced-motion: no-preference) {
  .hero-card {
    animation: slide-up 0.6s ease-out both;
  }
}

Motion is opt-in. Anyone with the setting on (and older browsers that don't support the query) get the static version. This is the safer default for new builds.

Pattern B: tone motion down for those who asked

@media (prefers-reduced-motion: reduce) {
  .parallax-bg {
    background-attachment: scroll;
    transform: none;
  }
  html {
    scroll-behavior: auto;
  }
}

This works well when retrofitting an existing site. MDN's own example swaps a pulsing scale animation for a gentler dissolve, which shows that "reduce" doesn't have to mean "nothing at all".

Avoid the blanket rule that sets every animation duration to near zero across the whole site. It can break components that rely on animation events to finish, and it removes helpful feedback along with the decoration.

Step 4: Handle JavaScript-driven motion

Carousels, scroll libraries and animated counters often run in JavaScript, where CSS alone won't stop them. web.dev's article shows the query can be checked from scripts too:

const reduceMotion = window.matchMedia('(prefers-reduced-motion: reduce)');

if (!reduceMotion.matches) {
  startCarouselAutoplay();
}

reduceMotion.addEventListener('change', () => {
  if (reduceMotion.matches) stopCarouselAutoplay();
});

Listening for changes means someone who flips the setting mid-visit gets the calmer version straight away. If you use an animation library, check its documentation for a built-in reduced-motion option before writing your own.

Step 5: Video and autoplay

Background and hero videos deserve their own decision. With reduced motion on:

  • Don't autoplay. Show the poster frame and a visible play button.
  • If the video carries information, keep it available, just not moving on load.
  • Give every autoplaying video a pause control for everyone, whatever the setting, since many visitors dislike autoplay.

Step 6: Test on real devices

  1. Turn on reduce motion on your phone and computer.
  2. Reload the site (some browsers pick up the change instantly, some on reload).
  3. Walk through the home page, a product or service page, the menu and the checkout or contact form.
  4. Check that nothing important disappeared. Content that only appeared via an animation should still be visible.
  5. Turn the setting off again and make sure the full experience still works.

Browser developer tools can also emulate the preference, which is handy while building, but finish with real devices.

Troubleshooting

  • A section is blank with reduced motion on. The content starts hidden and only an animation reveals it. Set the visible state as the default and animate from hidden only inside the no-preference block.
  • The carousel still auto-advances. It's controlled by JavaScript; add the matchMedia check.
  • Third-party widgets still animate. Chat bubbles and review badges may not respect the setting. Check their settings or contact the vendor.

Where this fits in accessibility guidelines

WCAG includes a success criterion on exactly this. MDN's summary of the Operable guidelines lists 2.3.3 Animation from Interactions (Level AAA): let users disable animations triggered by interaction, unless the animation is essential. Treat it as a design benchmark; building with the media query from the start makes meeting it straightforward.

FAQ

Does reduced motion mean no animation at all?

No. It means removing non-essential motion and softening the rest. Fades, colour changes and quick transitions are usually fine.

Will this hurt my site's design?

Only for visitors who asked for less motion, and they'll prefer it. Everyone else sees the full design.

Should I add a motion toggle on the site itself?

It's optional. Respecting the system setting covers most people; a site-level toggle helps visitors who haven't found the setting.

Does the setting affect performance?

Indirectly. Skipping heavy parallax and autoplay video can make pages lighter for those visitors.

A short motion audit is often the quickest accessibility win on an animated site, so send us the pages that move the most and we'll suggest what to keep.

Sources

WhatsAppLet’s talk