Resource · Checklist

Motion accessibility checklist

Use it on each animated or WebGL component before design review and before launch, checking with reduced motion on and off.

Free, no sign-up. Updated .

The WCAG 2.2 criteria are 2.2.2 Pause, Stop, Hide (Level A), 2.3.1 Three Flashes or Below Threshold (Level A) and 2.3.3 Animation from Interactions (Level AAA). A site can pass all three and still make people unwell, so some items go further. The reasoning is in Reduced motion is a design spec, not an off switch.

The spec

  • Each animated component has a written reduced-motion state: what it does instead, not just that it stops.
  • Each parallax, zoom, large slide or camera move is listed with its reduced-state replacement.
  • Short fades and colour changes confirming an action stay in the reduced state.
  • Nothing a visitor needs (text, a control, a price) appears only inside an animation.

Reading the preference in code

  • Search the CSS for animation and transition: each sits inside @media (prefers-reduced-motion: no-preference) or is a short opacity change.
  • Each JavaScript animation, scroll-linked timeline or canvas render loop reads matchMedia('(prefers-reduced-motion: reduce)').
  • Changing the OS setting with the page open updates it without reload (the code listens for change).
  • With reduced motion on, no smooth-scroll library runs; the page scrolls natively.
  • Elements that fade or slide in are visible on load in the reduced state and with JavaScript off.

Pause, stop, hide (WCAG 2.2.2)

  • Motion that starts by itself, lasts over 5 seconds and sits beside other content has a visible pause control, background video and WebGL included.
  • The pause control is keyboard-operable, has an accessible name and comes early in the tab order.
  • Carousels and tickers don't auto-advance, or stop when paused, hovered or focused.
  • A site motion toggle starts from the OS setting, and the choice survives a reload.

Flashing (WCAG 2.3.1)

  • Screen-record shader effects, glitch transitions or particle bursts and step through frame by frame: nothing flashes over 3 times in any second.
  • Those recordings pass PEAT (Photosensitive Epilepsy Analysis Tool), which also tests saturated red.

Scrolling and input

  • One wheel notch or swipe scrolls as far as it would without your scripts.
  • Arrow keys, Page Up/Down, Space and Home/End scroll normally.
  • A pinned or scroll-driven section can be passed at reading speed without skipping content.
  • Hover, tap and drag animations are off in the reduced state (WCAG 2.3.3) unless the motion is the task.
  • Anything revealed on hover also appears on tap and keyboard focus.

Focus and screen readers

  • No animation moves focus, and no moving layer covers the focused element.
  • After an animated change of view, focus lands on the new view's heading.
  • Decorative canvases have aria-hidden="true"; informative ones have a text or HTML equivalent.

Fallbacks

  • With WebGL disabled, the designed fallback shows and links and forms work.
  • Forcing a lost context with WEBGL_lose_context shows the fallback, not a blank canvas.
  • Text over an animated background passes AA contrast on its lightest and darkest frames and the fallback (screenshot each, then run a contrast checker).

Testing

  • Reduced motion emulated in Chrome DevTools (Rendering panel) on each key page.
  • The real OS setting tested on one desktop and one phone.
  • Keyboard-only pass done with motion on and off.
  • Screen reader pass on each page with a canvas or animated transition.
  • On a low-end Android phone, a remote-debugging Performance recording shows no long runs of dropped frames; in our experience stutter is as uncomfortable as excess motion.

For how we build both motion states together, see motion and interaction.

Want a second pair of eyes on it?

Start a project and we will tell you plainly where the risks are.