Skip to main content

WCAG 2.3.2 — Three Flashes

AAA

At AAA, the small-area exception that 2.3.1 grants is gone. Anything that flashes more than three times per second fails — regardless of how small or dim it is.

What this requires

Content must not contain anything that flashes more than three times in any one-second period. Unlike 2.3.1, there is no exception for small or low-luminance flashing areas. The AAA position is the simplest one: don't flash more than three times per second, anywhere, ever.

How AI coding tools fail this

Same failure shapes as 2.3.1, with the small-area exemption removed: small flashing indicators (a 12-pixel notification dot that pulses at 6 Hz), strobing favicon updates, and animated cursors on busy or loading states.

The second pattern unique to 2.3.2: "below threshold" arguments that work at AA fail at AAA. A team that has been relying on the small-area or low-luminance exception in 2.3.1 has to redesign for AAA.

Edge cases

  • AAA bar. Don't target this if AA is the project's level.
  • prefers-reduced-motion still doesn't satisfy the criterion by itself — but layer it on for users who opt in.
  • The 3 Hz floor is consistent across 2.3.1 and 2.3.2. The difference is in what counts as exempt.
  • PEAT analysis still applies. The AAA position is mostly about removing exceptions, not changing the underlying physics.

How Jeikin handles this

The same scanner output that feeds 2.3.1 is reused for 2.3.2, with the AAA exceptions disabled. The dashboard maps each finding to both criteria when a project targets AAA.

References