Designing motion for accessibility
Respecting reduced motion preferences and designing movement that works for everyone.

Zander Whitehurst
7 min read
Motion can make an interface easier to understand. It shows where things came from, what changed and what to pay attention to. For some people, though, the same motion causes real physical discomfort. Designing motion responsibly means holding both of those truths at once.
This is not about stripping animation out of your product. It is about understanding who motion can harm, offering a comfortable alternative and giving people control over their own experience.
Who motion affects
The group most affected is people with vestibular disorders. The vestibular system, in the inner ear, helps us balance and understand how we are moving through space. When it is disrupted, by conditions like vestibular migraine, labyrinthitis or after a concussion, the brain can struggle to reconcile what the eyes see with what the body feels.
On screen, that mismatch shows up when large areas of the interface move, especially when the movement suggests the viewer is moving. Parallax, zooming, full screen slides and scroll triggered effects are common culprits. The result can be dizziness, nausea, headaches or disorientation, sometimes lasting hours after the screen is closed.
Vestibular disorders are more common than most people assume, and many people experience milder sensitivity without a diagnosis. Motion also affects others:
- People with attention related conditions can find constant movement distracting enough to stop them completing a task.
- People with photosensitive epilepsy can have seizures triggered by flashing content.
- People with migraines may find certain movements or flashes trigger an attack.
Using prefers-reduced-motion
Every major operating system has a setting that lets people ask for less motion. Browsers expose that preference through the prefers-reduced-motion media query, which means you can detect it and adapt.
The simplest approach in CSS is to define your default motion and then adjust it inside the media query. In Motion for React, the useReducedMotion hook gives you the same information in a component.
Two principles make this work well:
- Treat it as a first class state. Design the reduced motion version of each animation deliberately, at the same time as the default, rather than bolting it on later.
- Test with it switched on. Turn on the setting on your own device and use the product for a day. You will find things you missed.
Reduce rather than remove
A common mistake is to respond to reduced motion by switching all animation off. It feels safe, but it often makes the interface harder to use. Motion was doing a job, and when it vanishes, that job goes undone.
Consider a panel that slides in from the side. In the default version the slide shows where the panel came from. If you simply remove the animation, the panel appears with a jarring snap. A better reduced version keeps a short opacity fade. Nothing moves across the screen, but the change is still soft and clear.
Most motion falls into one of two types:
- Motion that moves things in space. Slides, zooms, parallax and large translations. These are the ones most likely to cause discomfort, and they should be replaced.
- Motion that changes appearance in place. Fades, colour changes and subtle opacity shifts. These are generally safe and make excellent replacements.
.panel {
transition: transform 250ms ease-out, opacity 250ms ease-out;
}
@media (prefers-reduced-motion: reduce) {
.panel {
transition: opacity 150ms ease-out;
transform: none;
}
}
Small, contained motion like a button scaling slightly on press is usually fine to keep. The risk comes from movement that is large, fast or covers a big part of the screen.
Autoplay
Content that moves on its own is one of the biggest accessibility problems in motion design. Carousels that rotate, background videos that loop and animated illustrations that never stop all compete for attention and can trigger discomfort.
The accessibility guidelines are clear here. Anything that moves, blinks or scrolls automatically for more than five seconds should have a way to pause, stop or hide it. In practice:
- Do not autoplay by default when reduced motion is turned on.
- Provide a visible pause control for any looping animation or video, even when reduced motion is off.
- Stop after a few cycles for decorative loops, rather than running forever.
Autoplaying carousels are worth questioning in general. Most people never see beyond the first slide, and the ones who try to read the second often find it disappears before they finish.
Parallax and scroll effects
Parallax, where background and foreground layers move at different speeds as you scroll, is one of the most common triggers for vestibular symptoms. It creates exactly the sense of depth and self motion that the inner ear struggles with.
Scroll driven effects more broadly carry similar risks. Elements that zoom, rotate or fly in as you scroll tie movement directly to the person's own action, which can amplify the mismatch.
If you use these effects, keep them subtle, keep the moving area small and turn them off entirely for reduced motion. The page should still read perfectly well as a static layout. If it does not, the content is relying on motion it should not need.
Flashing
Flashing content is the one area where the risk is not discomfort but harm. Content that flashes more than three times in any one second can trigger seizures in people with photosensitive epilepsy, and saturated red flashes are particularly dangerous.
This rarely comes up in standard interface design, but it does appear in celebratory effects, glitch styles, video content and attention grabbing alerts. The rule is simple: never flash more than three times per second, and avoid large areas of rapidly alternating contrast altogether. This applies regardless of any user setting.
Giving users control
The operating system setting is a good start, but not everyone knows it exists, and some people only want less motion in certain products. Offering your own control respects that.
A motion preference in your product settings, with options like "System default", "Reduced" and "Full", lets people choose without digging through their device. It also signals that you have thought about it, which builds trust with the people who need it most.
A few years ago, a student in one of my cohorts quietly mentioned that she could not watch half of the examples I showed on the first day. She had a vestibular condition, and the showreels I loved made her feel seasick. I had been teaching motion for years and had never thought to ask. Since then I open every course by explaining reduced motion and showing how to design for it, before showing a single flashy example. It changed how I teach, and it changed how my students design.
A practical checklist
When reviewing motion for accessibility, work through these questions:
- Does it respect reduced motion? Every animation should have a deliberate reduced version.
- Is anything large moving through space? Replace it with a fade for reduced motion.
- Does anything autoplay? Make sure it can be paused and does not autoplay for reduced motion.
- Is there parallax or scroll triggered movement? Keep it subtle and turn it off for reduced motion.
- Does anything flash? Never more than three times per second.
- Can people choose? Consider an in product motion setting.
Accessible motion is better motion
Designing for accessibility tends to improve motion for everyone. It pushes you to ask what each animation is really for, to prefer subtle movement over spectacle and to make sure the interface works without relying on movement at all.
If you want to practise building motion that is both expressive and accessible, the AI Motion Design bootcamp treats reduced motion as a core part of every project. Whatever you are working on, turn on reduced motion today and spend ten minutes with your product. It is the quickest accessibility audit you will ever run.
Memorisely