Free scan

November 13, 2026

Animations, Accessibility and Reduced Motion: Pause, Flashing and prefers-reduced-motion Under WCAG

Animation can guide the eye, but it can also distract, make people feel sick or, in the case of flashing, trigger a seizure. When it comes to animations, accessibility and reduced motion, WCAG 2.2 sets out three complementary rules: let users pause, stop or hide anything that moves on its own (Success Criterion 2.2.2, Level A), let users disable animation triggered by interaction (Success Criterion 2.3.3, Level AAA), and never let content flash more than three times per second above the thresholds (Success Criterion 2.3.1, Level A). The prefers-reduced-motion CSS media query, which reflects the user's "reduce motion" setting, is one of the sufficient techniques the W3C lists for 2.3.3. Below, we walk through what each criterion requires, what is exempt, and how to put it into practice.

SC 2.2.2 Pause, Stop, Hide: giving users control over moving content

Success Criterion 2.2.2 (Level A) has a simple goal: fewer users distracted by content that moves or updates while they are trying to interact with the page. The W3C names people with low literacy, reading or intellectual disabilities, and attention deficit disorders, as well as anyone who has trouble reading text quickly or tracking a moving object.

For moving, blinking or scrolling content, the requirement applies when three conditions are all met: it starts automatically, it lasts more than five seconds, and it is presented in parallel with other content. In that case, there must be a mechanism for the user to pause, stop or hide it, unless the movement is part of an activity where it is essential. For auto-updating content (stock prices, weather radar), there is no five-second allowance: as soon as it starts on its own and is shown alongside other content, the user must be able to pause, stop or hide it, or control how often it updates, unless the auto-updating is part of an activity where it is essential.

Why five seconds? According to the W3C, it is long enough to catch the user's attention, yet short enough that they can simply wait it out. Brief blinking is therefore acceptable, as long as it stops or can be stopped.

SC 2.2.2: exceptions, examples and techniques

Whether content is presented in parallel with other content is the deciding factor. A loading screen that is the only thing on the page and asks the user to wait needs no control, even if it runs longer than five seconds. The W3C notes that an animation during a preload phase can be essential if no interaction can happen during that phase and if showing progress matters to the user. Likewise, a 15-second full-page ad that every user must watch before reaching free content needs no control, because it is not displayed alongside other content.

The passing examples the W3C gives are very concrete: an ad that blinks and then stops after five seconds; a blinking arrow next to a form's submit button that stops after five seconds; an animation with a "freeze animation" button near its bottom edge; a stock ticker with pause and restart buttons that, on restart, tells the user the data is delayed and offers a button to jump to the latest trade; and an essential process animation with pause and restart buttons.

On the other side, the W3C documents typical failures: F16, scrolling content where the movement is not essential and no mechanism to pause and restart is provided; F112, blinking content that lasts more than five seconds with no way to stop it; F50, a script that causes a blink effect with no mechanism to stop it within five seconds or less; and F7, an object or applet that moves or blinks for more than five seconds without a way to pause it. The W3C also lists sufficient techniques for meeting the criterion:

SC 2.3.3 Animation from Interactions: reduced motion and prefers-reduced-motion

Success Criterion 2.3.3 (Level AAA) requires that motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed. It complements 2.2.2: that criterion covers what the page animates by itself, while 2.3.3 covers what the user's action triggers. A single animation can, in fact, fail both.

What is at stake is physical. Motion triggered by scrolling, beyond the movement inherent in scrolling itself, can set off vestibular reactions. The W3C mentions distraction, dizziness, headaches and nausea, and points out that these reactions can be severe: nausea, migraines, even the need for bed rest. Parallax scrolling, where background and foreground move at different speeds, is often non-essential.

In WCAG terms, motion animation means adding steps between two states to create the illusion of movement or a smooth transition. An element that slides into place or changes size as it appears is animated; an element that appears instantly is not. The W3C states in its errata that the definition no longer excludes blurring.

To reduce the risk, the W3C says any one of these options is enough: avoid unnecessary animation, provide a control that turns off non-essential animation triggered by interaction, or rely on the "reduce motion" feature of the browser or operating system. This is where prefers-reduced-motion comes in: technique C39 is Using the CSS prefers-reduced-motion query to prevent motion, and technique SCR40 queries the same media query from JavaScript. A third technique lets users set a preference of their own that prevents animation.

SC 2.3.1 Three Flashes or Below Threshold

Success Criterion 2.3.1 (Level A) says web pages must not contain anything that flashes more than three times in any one-second period, unless the flash is below the general flash and red flash thresholds. People with photosensitive epilepsy or other photosensitive seizure disorders can have a seizure when content flashes at certain frequencies. Red flashing is more provocative, which is why it gets its own test.

The difference between blinking and flashing matters. Blinking is a distraction issue: it can be tolerated briefly if it stops or can be stopped. Flashing cannot be allowed even briefly, and offering a way to turn it off is not a valid fix, because a seizure could occur before the user has time to react. Blinking faster than three times per second counts as flashing.

For the thresholds, the W3C uses a reference rectangle of 341 × 256 CSS pixels, or 87,296 CSS pixels, representing a 10-degree visual field: the central vision area where people are most susceptible. Content with no more than three flashes in any one second passes automatically, with no analysis tool needed. Beyond that, content only conforms if the flashes stay below the general flash and red flash thresholds, for example because the combined area of concurrent flashes is no more than 0.006 steradians, or 25% of a 10-degree visual field. An analysis tool such as the Trace Center's PEAT (Photosensitive Epilepsy Analysis Tool) helps verify this.

Animations, accessibility and reduced motion: a practical audit method

Start with an inventory: carousels, scrolling banners, live-updating feeds, animated GIFs, videos, and effects on hover, click or scroll. For each item, ask three questions taken from the criteria: does it start on its own? Does it last more than five seconds? Is it shown alongside other content? If the answer to all three is yes, or if it is auto-updating content that starts on its own and is shown alongside other content, and unless the movement or updating is essential to the activity, check that a pause, stop or hide control exists (or a frequency control for updates), that it can be reached without trapping focus, and that it actually works.

For animation triggered by interaction, turn on your operating system's reduce motion setting and reload the page: to meet Success Criterion 2.3.3 (Level AAA), any non-essential effects you keep, such as parallax or page transitions, should then disappear, or a control on the site should let users switch them off; the other route is simply to avoid unnecessary animation altogether. Finally, identify anything that could flash more than three times per second and run those sequences through an analysis tool rather than trusting your eyes.

Keep the levels in mind: 2.2.2 and 2.3.1 are Level A, while 2.3.3 is Level AAA. To keep track of these points over time, you can run a free test of your pages and then set up continuous monitoring.

Frequently asked questions

What is prefers-reduced-motion in accessibility?

It is a CSS media query that lets a page respect the "reduce motion" preference the user has set. The W3C lists it as a sufficient technique for WCAG Success Criterion 2.3.3, both in CSS (C39) and in JavaScript (SCR40).

Does an auto-rotating carousel need a pause button?

Yes, if it starts on its own, lasts more than five seconds and is shown alongside other content: Success Criterion 2.2.2 then requires a way to pause, stop or hide it, unless the movement is essential to the activity.

What is the difference between blinking and flashing in WCAG?

Blinking is a distraction issue, tolerated briefly if it stops or can be stopped (Success Criterion 2.2.2). Flashing can trigger seizures and must not exceed three times per second above the thresholds (Success Criterion 2.3.1). Blinking faster than three times per second counts as flashing.

Is a button to turn off flashing content enough?

No. According to the W3C, turning off flashing after the fact is not a valid fix, because a seizure could occur before the user is able to react. The content has to stay within the threshold from the start.

Is parallax scrolling banned by WCAG?

No, but it is often non-essential and can trigger vestibular reactions. To meet Success Criterion 2.3.3, which is Level AAA, users must be able to disable it, for example through a site-wide control or by respecting the reduce motion preference.

Does an animated loading screen need a pause control?

Not if it is the only content on the page: the W3C states that a loading screen that is not shown in parallel with other content needs no control, even beyond five seconds.

Further reading on Conformly

Sources

This article relies on the official sources listed at the end of the page.