Motion and Interaction · Step 6 · 6 min read
Vestibular disorders and reduced motion
For some people, motion on a screen causes dizziness, nausea or migraine, sometimes for hours. What the vestibular system does, which kinds of on-screen motion are most likely to trigger symptoms, where the reduce-motion setting lives on each device, and how a page can hear it.
Motion you find delightful can make someone else lie down for the afternoon. That isn't a figure of speech. People with vestibular disorders can get dizzy, nauseous or a migraine from large movement on a screen, and the symptoms can last long after the animation stops. The good news is that they've already told you what they need: there's a switch on their phone and computer, and your page can read it.
What you'll be able to do after reading:
- Explain what the vestibular system does and why screen motion can upset it
- Name the kinds of motion most likely to trigger symptoms
- Find the reduce-motion setting on the main devices
- Read that setting in CSS, and know what it does and doesn't promise
1. The inner ear and the screen
Your sense of balance comes from several signals at once: your eyes, the muscles and touch sensors in your legs, and the vestibular system, a maze of fluid-filled canals and organs in the inner ear that senses movement and gravity. The brain compares them all to keep you upright and your eyes steady (NIDCD, Balance disorders).
A vestibular disorder is any disease, damage or injury to that system, like labyrinthitis or benign paroxysmal positional vertigo (Val Head, A List Apart, 2015). It's not rare. In the United States, about 15% of adults, 33 million people, had a balance or dizziness problem in 2008, from many causes (NIDCD), and the risk grows with age.
Here's why screens matter. When your eyes see large movement but your inner ear feels none, the signals disagree. For most people that's fine. For people whose vestibular system is already struggling, it can be enough to bring on symptoms: dizziness, nausea, headaches, and in WCAG's words, sometimes "potentially needing bed rest to recover" (W3C, Understanding 2.3.3). Motion can also affect people with migraine and epilepsy (flashing is a separate risk, covered in WCAG and motion).
2. What kind of motion triggers it
Not all motion is a problem. Val Head talked to people with vestibular disorders for her 2015 article in A List Apart, and found three factors that matter most (A List Apart, Designing Safer Web Animation for Motion Sensitivity):
| Factor | Riskier | Safer |
|---|---|---|
| Size of the movement, relative to the screen | A full-screen wipe or zoom | A small button rotating in place |
| Direction and speed | Parallax, and anything moving at a different speed or in a different direction from your scroll | Content that moves exactly with your finger |
| Distance travelled | A zoom that flies "through" a lot of virtual space, like the iOS 7 transitions | A short slide of a few pixels |
And one more line from the same article that's worth keeping: animations of properties that don't move, like opacity, colour and blur, are unlikely to be a problem. WCAG draws the same line: its definition of motion animation excludes changes of colour, blur or opacity that don't change an element's perceived size, shape or position (W3C, Understanding 2.3.3). That's why "fade instead of move" is the most useful reduced-motion move you have.
3. The setting people already use
Right now your device is not asking for reduced motion. The page sees prefers-reduced-motion: no-preference.Right now your device is asking for reduced motion. The page sees prefers-reduced-motion: reduce.
| Device | Where the setting lives |
|---|---|
| iPhone and iPad | Settings › Accessibility › Motion › Reduce Motion |
| Mac | System Settings › Accessibility › Motion › Reduce motion (on older versions, under Display) |
| Windows 11 | Settings › Accessibility › Visual effects › Animation effects (off) |
| Android 9 and later | Settings › Accessibility › Remove animations |
| GNOME (Linux) | Settings › Accessibility › Seeing › Reduced animation |
Every major system has a setting to reduce motion. When someone turns it on, the browser reports it to every page through one media query, prefers-reduced-motion, with two values: no-preference and reduce (MDN, prefers-reduced-motion). It has worked in every major browser since 2020 (webstatus.dev). On iPhone, turning it on also changes the system's own effects: screen transitions dissolve instead of zooming or sliding, and the parallax of wallpaper, apps and alerts when you tilt the phone is turned off (Apple Support, Reduce screen motion). Apple's own answer is the same pattern you'll use: dissolve instead of move.
The figure's live line uses nothing more than that media query:
.mo-c-if-reduce { display: none; }
@media (prefers-reduced-motion: reduce) { .mo-c-if-reduce { display: revert; } .mo-c-if-motion { display: none; } }
4. What the setting means, and what it doesn't
- It means "less motion", not "no motion". The person didn't ask for a broken page. Feedback, state changes and progress still need to be visible, just without large movement. A fade, a colour change or an instant swap usually does it.
- It's not only for people with a diagnosis. People turn it on for migraine, for motion sickness, for focus, or because animations feel slow. You don't need to know why.
- Not everyone who needs it knows it exists. That's why WCAG also lists avoiding unnecessary animation and offering an on-page control as ways to help (W3C, Understanding 2.3.3). The setting is the floor, not the ceiling.
- It's a preference for your page, too. Nothing happens unless the code checks it. Every animation in this course does, which is the subject of Designing a reduced-motion version.
5. Common mistakes
- Treating the setting as "turn every animation off", including feedback people need.
- Big parallax and scroll-linked effects with no reduced version.
- Thinking motion sensitivity is too rare to plan for.
- Testing reduced motion never, because nobody on the team has it on.
- Using
prefers-reduced-motiononly for one hero animation and forgetting transitions, carousels and videos that autoplay.
6. Vocabulary
| Term | Meaning |
|---|---|
| Vestibular system | The part of the inner ear that senses movement and gravity, and helps balance and keep vision steady |
| Vestibular disorder | Any disease, damage or injury to that system |
| Parallax | Background and foreground moving at different speeds |
| Reduce motion | The system setting that asks apps and pages for less movement |
prefers-reduced-motion |
The CSS media query that reads that setting: no-preference or reduce |
7. Try it (no tools needed, just your phone)
- Turn on Reduce Motion on your phone, using the path in the figure.
- Open three apps and two websites you use, and do what you always do.
- Note what changed, what didn't, and anything that still moved a lot.
Reflection questions: Did any app feel broken with the setting on? Did any website change at all? What would you want your own product to do?
8. If you already practise
- Keep reduce motion on for a whole day each quarter. You'll find the gaps quickly.
- Add the setting to your test matrix, next to dark mode and large text.
- Rank the motion in your product by Val Head's three factors: size, direction, distance. Start the fixes at the top.
Checklist
Learn more
- Val Head, Designing Safer Web Animation For Motion Sensitivity (A List Apart, 2015)
- NIDCD, Balance disorders
- W3C, Understanding 2.3.3, Animation from Interactions
- MDN, prefers-reduced-motion · Apple Support, Reduce screen motion
- The A11Y Project, A primer to vestibular disorders
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
Accessibility fundamentals · Inclusive design · WCAG and motion · Designing a reduced-motion version · Scroll and motion