Marcus Andrey Study
Ler em português Library

Motion and Interaction · Step 6 · 7 min read

WCAG and motion

Four WCAG success criteria cover motion: pausing things that move by themselves, flashing that can cause seizures, and turning off motion that interactions trigger. What each one asks in plain words, its level, how to test it, and the techniques W3C lists to meet it.

WCAG asks three things of motion: let people stop it, never let it flash, and let them turn it off. The Web Content Accessibility Guidelines are long, but the parts about motion are short and clear. Two are level A, the minimum every product should meet. Two are AAA, the highest level, and one of those costs so little to meet that there's no good reason not to.

What you'll be able to do after reading:

  • Explain the four motion criteria of WCAG 2.2 in plain words
  • Tell whether a moving element needs a pause, stop or hide control
  • Recognise flashing that's a seizure risk
  • Test a page against each criterion, with the techniques W3C lists

1. The four criteria

Criterion Level In plain words How to test
2.2.2 Pause, Stop, Hide A Anything that moves, blinks or scrolls by itself for more than five seconds, next to other content, can be paused, stopped or hidden. Auto-updating content too Load the page and wait. Does anything keep moving? Find the control
2.3.1 Three Flashes or Below Threshold A Nothing flashes more than three times in any one second, unless the flash is below the general and red flash thresholds Look for strobes, flickering, fast cuts in video; analyse doubtful content with a flash tool
2.3.2 Three Flashes AAA Nothing flashes more than three times in any one second, at all The same, with no threshold exception
2.3.3 Animation from Interactions AAA Motion that an interaction triggers can be turned off, unless it's essential Turn on reduce motion; scroll, tap and navigate; does anything still travel?

Sources: W3C, Understanding 2.2.2 · 2.3.1 · 2.3.2 · 2.3.3.

The split between 2.2.2 and 2.3.3 is about who started the motion. If the page starts it by itself, it's 2.2.2. If a person's action starts it, a tap, a scroll, a navigation, it's 2.3.3. W3C notes that one animation can fail both (W3C, Understanding 2.3.3).


2. Pause, Stop, Hide in practice

Porto Ferry service back to normal Lisbon Line 2 closed until Friday Braga New cycle lanes open on Monday Faro Airport shuttle every 20 minutes
The ticker starts by itself and runs for more than five seconds, so it needs a control

Your device asks for reduced motion, so the ticker doesn't move at all: the four updates sit still, as a list.

An auto-moving ticker that passes WCAG 2.2.2, Pause, Stop, Hide. It starts on its own and goes on for more than five seconds beside other content, so the person gets a real pause: the switch, and the pointer resting on it. The text exists once for screen readers; the copy that makes the loop seamless is hidden from them. With reduced motion on, it doesn't move at all.

The ticker starts by itself, runs for more than five seconds, and sits beside other content: all three conditions of 2.2.2. So it gets a pause. This is the code that runs it:

@media (prefers-reduced-motion: no-preference) {
  .mo-c-tick__belt { animation: mo-c-belt 30s linear infinite; }
  .mo-c-tick:has(.mo-c-pause:checked) .mo-c-tick__belt,
  .mo-c-tick__window:hover .mo-c-tick__belt { animation-play-state: paused; }
}
@keyframes mo-c-belt { to { transform: translateX(-50%); } }

Three things to see in it. The motion is opt-in: it only exists inside no-preference, so with reduced motion on, it never starts. The pause is a real control, a checkbox you can reach with the keyboard, which is technique G186 (W3C, G186). And pausing keeps its place: animation-play-state freezes the belt where it is and resumes from there, as technique G4 describes (W3C, G4). Hover alone isn't enough, because touch and keyboard users can't hover.

The same rule applies to carousels that advance by themselves, background videos, animated GIFs in content, and live feeds. One exception is narrow: a loading animation can count as essential when nobody can interact during that phase and no indicator would make people think the page froze (W3C, Understanding 2.2.2, note 4).


3. Flashing: a hard limit

Flashing is different from other motion: it can trigger seizures in people with photosensitive epilepsy, and W3C notes that people are even more sensitive to saturated red flashing. That's why 2.3.1 applies to everything on the page, even content that isn't used to meet any other criterion (W3C, Understanding 2.3.1).

For interface design, the rule is easy: don't flash. No blinking alerts, no strobing "attention" effects, no fast black-and-white toggles. Where you can't control it, like user videos or marketing films, analyse the content with a flash-testing tool, as technique G15 describes (W3C, Understanding 2.3.1).


4. Animation from Interactions: AAA that's cheap

2.3.3 is level AAA, and many teams stop reading there. Don't. The sufficient technique W3C lists is the media query you already know, prefers-reduced-motion (W3C, C39). C39 even shows both ways to write it: turn motion off inside reduce, or only turn it on inside no-preference.

Two details from the Understanding document help you decide what to keep:

  • Scrolling itself is essential. Moving new content into view when someone scrolls is fine; it's the extra motion added to scrolling, like parallax or elements flying in from the side, that should be possible to turn off.
  • Fading is not motion animation in WCAG's definition: changes of colour, blur or opacity that don't change an element's perceived size, shape or position don't count (W3C, Understanding 2.3.3). A reduced version can still fade.

5. Common mistakes

  • A carousel that advances by itself with no pause, or a pause button that only appears on hover.
  • An animated GIF in content that loops forever.
  • Pausing on hover only.
  • A blinking "new" badge or a flashing error.
  • Ignoring 2.3.3 because it's AAA, when one media query meets it.

6. Vocabulary

Term Meaning
Success criterion One testable requirement of WCAG
Level A, AA, AAA Conformance levels: A is the minimum, AA is what most laws and policies ask for, AAA is the highest
Starts automatically Motion the page begins without a person's action
Essential Motion you can't remove without changing what the content is or does
Flash A pair of opposing changes in brightness, the kind that can trigger seizures
Sufficient technique A way of meeting a criterion that W3C has documented as enough

7. Try it (no tools needed)

  1. Open a news site or a shop's home page. Don't touch anything for ten seconds.
  2. List everything that moved by itself. For each, is there a way to pause, stop or hide it?
  3. Now scroll the page. List the motion your scroll triggered. Which of it is essential?

Reflection questions: Which item on your list would fail 2.2.2? If you could change one thing on that page, what would it be?


8. If you already practise

  • Add the four criteria to the motion checklist in your design system, with the test for each.
  • Make "auto-advance off by default" the rule for carousels in your components.
  • Ask for 2.3.3 in your accessibility target even if the policy says AA: it's nearly free with motion tokens and one media query.
  • Keep flashing out of the brand's motion language entirely.

Checklist

Learn more

Books, courses and videos to go deeper

Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Accessibility fundamentals · Vestibular disorders and reduced motion · Designing a reduced-motion version · Feedback while waiting · Audit a page for reduced motion

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close