Motion Should Ask Permission

There is a moment in every motion review where someone says "can it do more?" And there is almost never a moment where someone asks "who does this hurt?" I want to talk about the second question, because for a meaningful slice of any audience, motion is not delight. It is dizziness, nausea, migraine, or a scattered train of thought that never recovers.

Vestibular disorders affect millions of people. Parallax scrolling, zooming transitions, spinning elements, and large areas of the screen sliding around can trigger genuine physical symptoms. Add everyone with ADHD trying to read a paragraph next to a looping animation, and "who does this hurt" stops being a niche question. It is a craft question, and studios that care about motion should be the best in the industry at answering it.

Reduced motion is not "no motion"

The mechanism is simple. Operating systems expose a user preference, and CSS lets us respect it with the prefers-reduced-motion media query. The lazy response is to wrap everything in it and kill all animation for those users. That is compliance, not design, and it usually breaks meaning: if your interface communicates state through motion, deleting motion deletes information.

The better practice is designing a reduced vocabulary, not an empty one:

• Replace movement with opacity. A crossfade communicates the same state change as a slide without moving the world.
• Kill the travel, keep the cue. A menu can appear instead of sweeping in. The affordance survives.
• Scale, gently, is usually fine. Large translations and parallax are the main offenders. A subtle 2 percent scale on hover rarely is.
• Never autoplay large motion. Looping hero videos and scroll-hijacked sequences should always have a reduced alternative, and honestly, a pause button for everyone.

On the Aperture product site we shipped last year, the full experience uses choreographed scroll sequences to explain the product. The reduced version replaces them with static compositions and crossfades that carry identical information. Building it added maybe six percent to the motion budget. Nobody who sees the reduced version experiences it as the broken one.

Make it a system decision, not a heroic one

The reason most teams fail here is not indifference, it is timing. Accessibility considered after the storyboard is expensive. Accessibility considered inside the motion system is nearly free. Our motion guidelines for every client now define each animation pattern with two states from day one: full and reduced. When a pattern is specified, both are specified. When one is built, both are built. It is the same discipline as designing dark mode alongside light mode instead of retrofitting it.

We also test it for real. Turning on "reduce motion" in system settings and actually using the site is a five-minute exercise that catches what audits miss, like the JavaScript-driven animation library that never checked the preference at all.

The opinionated part

Some designers hear all this as a leash. I think that is backwards. Constraints are what make motion design a discipline instead of a mood. Choreographing a sequence that communicates in both a full and a reduced vocabulary is simply harder and better work than making things fly around. And the discipline pays back everywhere: motion that survives the reduced test is almost always motion with a clear communicative job, which means the full version gets sharper too.

Motion is powerful precisely because the human visual system cannot ignore it. That is a strong drug. Dose accordingly, and ask permission.