Three Flashes Rule: Avoid Seizure-Triggering Content
Also called: Three Flashes or Below Threshold, Flash threshold, Photosensitive seizure rule
Definition
The three flashes rule is WCAG success criterion 2.3.1 Three Flashes or Below Threshold: web pages must not contain anything that flashes more than three times in any one-second period, unless the flashing stays below the general flash and red flash thresholds.
The three flashes rule protects people who can have a seizure when they see flashing light. Anything on a page – a video, an animated banner, a GIF, a strobe effect in a hero section – may flash at most three times in any one second, or the flashing must be so small or so weak that it stays below the official flash thresholds. Unlike most accessibility barriers, a violation here can physically harm someone within seconds.
What it means
WCAG 2.3.1 Three Flashes or Below Threshold is a Level A criterion in WCAG 2.2 and part of EN 301 549 as clause 9.2.3.1. A page passes if one of two things is true:
| Option | What it means |
|---|---|
| Three flashes or fewer | Nothing flashes more than three times in any one-second period |
| Below the thresholds | The flashing area is small enough: concurrent flashes cover no more than 0.006 steradians within any 10-degree visual field – about 25 % of that field at typical viewing distance |
W3C defines a general flash as a pair of opposing changes in relative luminance of 10 % or more of the maximum, where the darker image is below 0.80 – a bright-dark-bright change, for example. A red flash is any pair of opposing transitions involving a saturated red. Red gets its own test because people are more sensitive to it.
For a practical estimate, W3C uses a 1024 × 768 reference screen and a 341 × 256 pixel rectangle anywhere on it. That rectangle is 87,296 pixels, about 11 % of the screen. Fine, balanced patterns such as white noise or a checkerboard with very small squares do not count as flashes.
Who benefits: people with photosensitive epilepsy and other seizure disorders can use the whole page instead of avoiding video and animation altogether. The stricter rule 2.3.2 Three Flashes (Level AAA) drops the threshold option – nothing may flash more than three times per second at all.
Examples
<!-- Risky: full-width strobe effect, 8 flashes per second -->
<div class="hero hero--strobe"></div>
<!-- Safer: slow fade, respects reduced-motion settings -->
<style>
.hero { animation: fade 4s ease-in-out infinite alternate; }
@media (prefers-reduced-motion: reduce) {
.hero { animation: none; }
}
</style>A slow fade over four seconds changes brightness far less often than three times per second. Honoring prefers-reduced-motion is good practice on top of that, but it does not replace staying under the limit – people who never set the preference must be safe too.
Keep flashing to three times per second or fewer, use slow fades instead of strobes, crop or shrink flashing video areas, check marketing videos and GIFs before upload, and warn before content that contains flashes.
Use full-screen strobe or lightning effects, rapid red-black alternations, fast-blinking "sale" banners, or video of explosions and camera flashes without checking it first.
How to check three flashes
Questions
What is the three flashes rule in WCAG?
It is success criterion 2.3.1 Three Flashes or Below Threshold: nothing on a web page may flash more than three times in any one second, unless the flashing stays below the general flash and red flash thresholds. It is Level A, so every conforming website must meet it.
Is a blinking cursor or blinking text a problem?
Usually not for 2.3.1. W3C notes that blinking rarely reaches three changes per second, though it can. A slow blink is fine here, but if it runs longer than five seconds next to other content, people need a way to stop it under 2.2.2.
Why is red flashing treated separately?
People are more sensitive to flashing involving saturated red. That is why WCAG defines a separate red flash threshold in addition to the general flash threshold.
Can an automated scanner detect flashing content?
Not reliably. A WCAG scanner checks the code of a page, while flashing depends on what a video or animation shows frame by frame. Check videos with a flash analysis tool and review animations manually; captions and other media rules need their own review.
What is the difference between 2.3.1 and 2.3.2?
2.3.1 (Level A) allows faster flashing if it stays below the area and brightness thresholds. 2.3.2 Three Flashes (Level AAA) does not – no more than three flashes per second, regardless of size.
Related terms
Pause, Stop, Hide: Control Moving Content
Pause, Stop, Hide is WCAG success criterion 2.2.2. Moving, blinking or scrolling content that starts automatically, lasts more than five seconds and appears alongside other content needs a way to pause, stop or hide it; auto-updating content needs a way to pause, stop or control how often it updates.
Read definition: Pause, Stop, Hide: Control Moving ContentCaptions: Accessible Video for Deaf Viewers
Captions are synchronized text versions of a video's audio: the dialogue, who is speaking and the non-speech sounds needed to follow it. WCAG 1.2.2 requires them at Level A for all prerecorded audio in synchronized media.
Read definition: Captions: Accessible Video for Deaf ViewersTiming Adjustable: Fair Time Limits and Timeouts
Timing Adjustable is WCAG success criterion 2.2.1. For each time limit set by the content, users can turn it off, adjust it to at least ten times the default or extend it after a warning – unless the limit is part of a real-time event, essential, or longer than 20 hours.
Read definition: Timing Adjustable: Fair Time Limits and Timeouts