Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing rendered HTML, interactive components, or design-system patterns related to Prevent seizure-triggering flashing content. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 14% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -16% | 0% |
| case-04 | ✗→✓ | ▲ Improved | -1% | 0% |
| case-05 | ✗→✓ | ▲ Improved | 13% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 37% | 0% |
Flashing content between 3-60 Hz can trigger seizures in people with photosensitive epilepsy—this is a critical safety requirement, not just an accessibility preference.
Verify no content flashes more than 3 times per second, and that any flashing content occupies less than 25% of the viewport. Test animated GIFs, videos, and CSS animations for rapid flashing patterns.
Remove or slow down rapid flashing animations. Use animation tools to measure flash frequency. Replace flashing effects with fade transitions or static alternatives that convey the same information.
Explain how flashing content between 3-60 Hz can trigger seizures in people with photosensitive epilepsy, and why this is a critical accessibility and safety requirement under WCAG 2.3.1.
Review the rendered markup and interactive states that affect Prevent seizure-triggering flashing content. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/accessibility/flashing-content
Other measured skills in the registry, with their headline benchmark lift.