- Level
- A
- Since
- WCAG 2.0
2.3.1 Three Flashes or Below Threshold
Nothing on the page may flash more than three times in any one second, unless the flashing stays small and weak enough to be below the general and red flash thresholds.
/ What it requires
Flashing at certain rates can trigger seizures in people with photosensitive epilepsy and other photosensitive seizure disorders, and saturated red flashing is the most dangerous. Unlike most criteria, this one cannot be met by giving the user a control: a seizure can start before anyone reaches a pause button. That is why WCAG lists it among the four criteria that apply to all content on a page, and why the flashing has to be removed at its source, in the video, the animated image or the script.
Content passes if nothing flashes more than three times in any one second, or if the flashing stays below the general flash and red flash thresholds. A general flash is a pair of opposing changes in relative luminance of 10 percent or more of the maximum, where the darker state is below 0.80. A red flash is a pair of opposing transitions involving a saturated red. Flashing is also below the threshold when the combined area flashing at once covers no more than 25 percent of any 10 degree visual field, which W3C estimates as a 341 by 256 pixel rectangle on a 1024 by 768 screen. A fine, balanced pattern such as white noise does not count.
/ How pages fail it
- A hero video cuts between bright and dark shots, or shows strobe light or lightning, more than three times a second over a large part of the screen.
- An animated GIF banner alternates between a white frame and a saturated red frame several times a second.
- An alert uses a CSS animation that switches the background of a large block between black and white every 100 milliseconds.
- A browser game or canvas effect fills the screen with rapid explosion flashes.
- A loading or error screen makes the whole viewport pulse between bright and dark several times a second.
/ How to check it yourself
- List everything that changes quickly: video, animated GIF, APNG and WebP images, CSS and canvas animation, effects in games and players. Anyone sensitive to flashing should leave the viewing to someone else or to a tool.
- Count the changes in any one second. If nothing flashes more than three times in a second, the content passes without further analysis.
- For anything faster, judge the size of the flashing area against a quarter of a 341 by 256 pixel rectangle at 1024 by 768, since a small area may still pass.
- Run video and screen recordings through a free analysis tool such as PEAT, the Photosensitive Epilepsy Analysis Tool from the Trace Center, which checks recordings against the flash thresholds.
- Check video at the largest size a user can view it, usually full screen, and analyse short animations while they loop, as W3C advises.
/ How to fix it
- Edit the video so that no bright or saturated red flash repeats more than three times in any one second, for example by slowing or cutting strobe sequences.
- Where some flashing has to stay, confine it to a small part of the frame, well under the area threshold.
- Slow CSS animations that alternate brightness so that each full cycle lasts longer than a third of a second, and avoid alternating to and from saturated red.
- Wrap motion and flashing effects in @media (prefers-reduced-motion: no-preference) so they never run for people who asked for less motion. This helps, but the content still has to stay below the thresholds for everyone.
- Replace a third-party clip or animation that flashes and cannot be edited. A warning or a pause button does not satisfy this criterion.
/ What our scanner checks
No automated check covers 2.3.1 in our scan. Measuring flashes means recording the page over time and counting luminance changes across an area, and the scan looks at the page at one moment. HTML_CodeSniffer posts only a reminder here, which is dropped. In a manual audit a person reviews video, animated images and canvas effects and runs anything doubtful through a frame analysis tool.
/ Who fails it, in our own measurements
The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
Is a warning before flashing content enough to meet 2.3.1?
No. The criterion has no exception for warnings or controls, because a seizure can begin before a user can react. Content either stays at three flashes or fewer in any second, or stays below the flash thresholds, or it fails. A warning is still a courtesy to people who react to flashing below the threshold, but it does not change the result.
What is the difference between 2.3.1 and 2.3.2?
2.3.1 Three Flashes or Below Threshold is level A and lets flashing pass when it is small or weak enough to stay below the general and red flash thresholds. 2.3.2 Three Flashes is level AAA and removes that allowance: nothing may flash more than three times in any one second, whatever its size or brightness.
Does blinking text fall under 2.3.1?
Usually it falls under 2.2.2 Pause, Stop, Hide instead. W3C separates blinking, which distracts and may run for a short time if it stops or can be stopped, from flashing, which can trigger a seizure and is not allowed even for a second. Blinking faster than three times a second counts as flashing and is judged under 2.3.1.
