Motion and Sensory Sensitivity Design is the practice of building interfaces that do not harm or overwhelm people with vestibular disorders, photosensitive epilepsy, or sensory-processing differences. It covers three related needs: reducing motion for people whom animation makes dizzy or nauseous, avoiding flashing that can trigger seizures, and lowering sensory load for people whom autoplay, sound, and competing movement overwhelm. Of all accessibility work, this is the area where getting it wrong can cause physical harm, not just frustration.
The mistake is to treat motion as pure decoration with no cost. Parallax scrolling, large entrance animations, and motion-heavy transitions can trigger dizziness, nausea, vertigo, and migraines in people with vestibular conditions, and web.dev notes that over a third of adults will experience some form of vestibular dysfunction by age 40. Flashing content is more serious still: content that flashes more than three times per second can trigger seizures in people with photosensitive epilepsy. These are not edge cases to style around; they are safety constraints.
The good news is that the platform gives you the controls. The prefers-reduced-motion media query reports the user's operating-system motion preference, so you can reduce or replace animation for anyone who asked for less. WCAG sets a hard, Level A safety rule against flashing. And the pause-stop-hide criterion requires giving users control over autoplaying motion. Respecting these is mostly a matter of treating less motion as the safe default.
The principle: respect prefers-reduced-motion, never flash more than three times per second, give pause/stop/hide control over autoplaying motion, and keep sensory load low by default.
Motion and sensory accessibility rests on a safety guideline, a user-preference signal, and clear thresholds.
WCAG Guideline 2.3 states the goal plainly, as MDN summarizes it: "Do not design content in a way that is known to cause seizures or physical reactions." Two success criteria make it concrete. SC 2.3.1 Three Flashes or Below Threshold (Level A) requires that pages "do not contain anything that flashes more than three times in any one second period," unless the flash is below the general and red flash thresholds. This is a basic, non-negotiable safety rule, not an advanced nicety. The Epilepsy Foundation of America working-group standard MDN cites defines a flash hazard precisely: luminance at or above 20 cd/m2, a frequency at or above 3 Hz, and a solid visual angle at or above 0.006 steradians (roughly 25 percent of screen area at typical viewing distance).
The user-preference signal handles vestibular needs. SC 2.3.3 Animation from Interactions (Level AAA) requires that motion animation triggered by interaction can be disabled unless it is essential, and the W3C names the prefers-reduced-motion CSS media query as a sufficient technique. The media query checks the user's OS-level motion setting, so a site can reduce or remove non-essential animation for users who have asked for less, addressing the dizziness, nausea, and migraines that motion can trigger. The honest boundary is the word essential: a loading indicator or a progress animation that conveys necessary information is exempt; a decorative parallax effect is not.
The control requirement handles autoplay and overload. SC 2.2.2 Pause, Stop, Hide (Level A) requires a mechanism to pause, stop, or hide any moving, blinking, or auto-updating content that starts automatically, lasts more than five seconds, and is shown alongside other content. This protects people who are distracted or overwhelmed by motion, including many with attention and sensory-processing differences, and it pairs with calm-by-default choices such as no autoplay sound.
Tooling has caught up on the dangerous part. The original Photosensitive Epilepsy Analysis Tool (PEAT) is retired; its successor, the Harding Flash and Pattern Analyzer, is what platforms like YouTube and Vimeo now run on upload to screen for flash risk. Screening media for flashing before it ships is now a standard, available step.
For Users: When a site respects reduced motion and never flashes, you can use it without getting dizzy, nauseous, or, in the worst case, having a seizure. Control over autoplay means it does not overwhelm you.
For Designers: Motion has a cost some users pay in their body. Design a reduced-motion alternative for every animation, keep transitions calm, and never rely on large movement or flashing for effect.
For Developers: The platform gives you the levers. Wire prefers-reduced-motion into your CSS and JS, screen media for flash risk before publishing, and add pause/stop/hide controls to autoplaying content.
For Accessibility: This is the safety-critical corner of accessibility. The three-flashes rule is Level A precisely because the consequence is a seizure. Treat it as a hard constraint, not a guideline to weigh against aesthetics.
Motion and sensory accessibility comes down to reduced-motion support, the flash rule, user control, and calm defaults.
Respect prefers-reduced-motion. Detect the OS setting and reduce or replace non-essential animation. Swap large movement for a simple cross-fade or no animation. Keep only motion that is essential to meaning.
Never flash more than three times per second. Treat the WCAG 2.3.1 threshold as a hard rule. Screen video and animation with a flash and pattern analyzer before publishing, and avoid rapid light-dark transitions and strobing entirely.
Give pause/stop/hide control. Any motion that auto-starts and lasts over five seconds, auto-advancing carousels, and auto-updating feeds need an obvious way to pause, stop, or hide them.
Keep sensory load low by default. No autoplay sound, no competing simultaneous animations, no surprise motion. Calm defaults help people with sensory-processing and attention differences, and everyone in a quiet room.
Design the reduced-motion path first. Treat less motion as the baseline experience and added motion as the enhancement, so the safe version is never an afterthought.