Browsers expose the system request for less motion as prefers-reduced-motion. Large movement through space (parallax, zooms, sweeping panels) can cause dizziness or nausea for people with vestibular disorders. A small fade rarely does.
So movement through space gets replaced, and feedback confirming an action stays.
Two promises: reduced motion and Pause
We keep these separate. The system setting is chosen once, often by people who need it everywhere. A pause control serves whoever is here now, including people who never found the setting.
On this site:
- With
reduceset, loops never start. The orb paints one still frame, each canvas on a service page draws once on entering view, and a project's film waits for a press of its play button. - Interaction-triggered motion is skipped too. A click on a project normally morphs its cover into the project page; with
reduceset, the page simply changes. - A Pause motion switch sits in every footer and the homepage hero. It stops everything that moves on its own for over five seconds, and the device remembers.
- Pausing removes the live orb and releases its WebGL context. The drawn CSS orb underneath stays, so nothing changes shape.
The switch works one way. Pressing Play under a reduce-motion setting doesn't start the loops: a site's own toggle may only ask for less.
What WCAG 2.2 requires
Three success criteria cover most motion decisions; the full text is in WCAG 2.2 (opens in a new tab).
| Criterion | Level | In short |
|---|---|---|
| 2.2.2 Pause, Stop, Hide | A | Moving content that starts automatically, lasts more than five seconds and sits alongside other content needs a way to pause, stop or hide it, unless the movement is essential. |
| 2.3.1 Three Flashes or Below Threshold | A | Nothing flashes more than three times in any one second, unless the flashes stay below the general and red flash thresholds. |
| 2.3.3 Animation from Interactions | AAA | Motion animation triggered by interaction can be disabled, unless it is essential to the functionality or the information conveyed. |
2.3.3 is Level AAA, and many organisations don't target it. We meet it on level 2 and 3 pages anyway, because those pages are built from interaction-triggered animation.
2.2.2 is Level A and applies whatever the preference. A WebGL loop running past five seconds needs a visible pause control, hence our switch.
Calm by default in CSS
Write motion inside a no-preference query, so the still state renders unless motion is wanted. This also stops elements waiting at opacity: 0 for a script that never runs.
/* Calm by default; motion only when the visitor has not asked to reduce it */
.reveal { opacity: 1; }
@media (prefers-reduced-motion: no-preference) {
.reveal { opacity: 0; transform: translateY(24px);
transition: opacity .6s, transform .6s; }
.reveal.is-in { opacity: 1; transform: none; }
}
JavaScript motion needs the same check, and must listen for changes, because people switch the setting mid-visit.
const reduce = matchMedia('(prefers-reduced-motion: reduce)');
function applyMotionPreference() {
if (reduce.matches) {
scroller?.destroy(); // back to native scrolling
scene?.renderStill(); // the designed still frame
} else {
scroller ??= initSmoothScroll();
scene?.play();
}
}
reduce.addEventListener('change', applyMotionPreference);
applyMotionPreference();
Canvas loops and smooth-scroll libraries usually leak, since no CSS rule reaches them. Audit them by name.
A still version for each effect
For each animated component, ask what the motion says, then find a calmer way to say it.
| Effect | What it says | With reduce set |
|---|---|---|
| Parallax layers | Depth | Layers fixed; depth carried by scale and overlap |
| Section slides in | Something new has arrived | A short fade, or nothing |
| Page-to-page morph | Continuity between views | An instant change, focus moved to the new heading |
| Scroll-linked camera path | Progress through a story | Discrete still frames advanced by scroll position |
| Ambient orb or field | Atmosphere | One still frame of the same scene |
| Smooth scrolling | Weight | Native scrolling; the library is never started |
| Button feedback | Your input registered | Unchanged: a colour or opacity change is not the problem |
We fill this table during design. Left to the end, the reduced state is whatever survives, often a page with holes.
Testing both states
Developer tools and Playwright can emulate the media query. Check each level 2 and 3 page twice: with reduce emulated, then with Pause pressed. The first removes movement through space; the second stops loops but keeps feedback.
Our motion accessibility checklist is the pre-launch pass; the motion and interaction service is where this work gets scoped.


