How to check flashing content without uploading it
Flashing content is the one accessibility failure that can send someone to hospital. Content that flashes more than three times a second, over a large enough area — especially in saturated red — can trigger a seizure in people with photosensitive epilepsy, and migraines or vertigo in many more. That is why WCAG makes it a Level A criterion, the most basic tier, with no exception for decorative intent.
This tool checks the risk where the file already is: on your own device. When you drop a video or GIF here, your browser:
- Decodes the file locally — video through the browser's own decoder, sampled at up to 10 frames per second; animated GIFs frame by frame with their real frame delays, using a small decoder built into this page.
- Measures every sampled frame — mean luminance, mean colour, and the fraction of the frame whose luminance changed by at least 10% since the previous frame. That fraction is the "area covered" the WCAG threshold turns on.
- Counts flashes the way WCAG defines them — a flash is a pair of opposing changes in luminance, so an 8 Hz strobe reports 8 flashes per second, not 16. Red flashes are counted separately, on the saturated-red and chromaticity test.
- Reports a verdict you can act on — PASS, CAUTION or FAIL, the worst one-second window, a per-second timeline, the worst moments with timestamps, and concrete fixes for exactly what failed.
What makes this checker different
The tool that tops the results for this search is a capable free video checker, but its free tier covers video files only — GIF checking sits in its paid cloud tier — and it needs a file before it can show you anything. The classic PEAT tool is a desktop download, and the newest live-page checker is a Chrome extension you have to install. This page is the only free, no-install, in-browser checker we found that covers all three things creators actually need to check: video files, animated GIFs (the most common flashing content on the web, and the format most likely to loop forever and autoplay), and pasted colour sequences for CSS animations and loading spinners — with instant demo patterns that show the verdicts working before you upload anything, and a live network-request counter so you can verify the privacy claim yourself.
When is checking the right choice — and when is it the wrong one?
Checking is right before you publish anything that moves fast: a video with strobe cuts, a reaction GIF, a loading spinner, a carousel, a banner ad, or a transition between high-contrast scenes. It is the wrong choice as a substitute for judgement: a clip can pass the numeric thresholds and still be unpleasant, and a clip that fails only in a small area still deserves a second look. It is also the wrong tool for broadcast certification — that needs the certified Harding test, not a web page.
Honest limitations
Screening, not certification
A PASS means no flashing risk was found in these frames at this sampling rate. It does not certify broadcast compliance and is not a legal sign-off.
Sampling can miss fast flashes
Video is sampled at up to 10 frames per second, so flashes faster than about 5 per second can be undercounted. The result states its sampling rate — read it.
No spatial-pattern detection
Stripes, checkerboards and other regular patterns can also provoke seizures, and this checker does not detect them. If your content has high-contrast repeating patterns, review it by eye.
Only the first 2 minutes
Long videos are analysed for their first 2 minutes only. Trim the clip to the flashing section and check that part if the risk is later in the video.
Area is approximated
WCAG's area test is 25% of 10 degrees of visual field at a typical viewing distance. This tool approximates it as 25% of the frame changing at once — a reasonable proxy, not an exact measurement.
It never changes your file
This tool only reports. Your original file is never modified — apply the fixes in your editor, export again, and re-check the new file here.