Blinking content refers to text or elements that repeatedly turn on and off to attract attention. While this effect may appear visually noticeable, uncontrolled blinking can interfere with reading, comprehension, and interaction, especially for users who rely on a stable visual presentation.
WCAG does not prohibit blinking outright. Instead, it places conditions on duration and user control. Blinking becomes an accessibility issue when users cannot stop it, hide it, or when it persists long enough to disrupt interaction.
WCAG Success Criterion
2.2.2 Pause, Stop, Hide (Level A)
For any moving, blinking, scrolling, or auto-updating content that:
- Starts automatically
- Lasts more than five seconds
- Is presented alongside other content
Users must be able to pause, stop, or hide the movement, unless it is essential.
Blinking content that stops within five seconds or can be controlled by the user does not fail this criterion.
Important Distinction: Blinking vs Flashing
Blinking and flashing are not the same in WCAG.
- Blinking refers to repeated on/off visual changes intended to draw attention.
- Flashing refers to rapid luminance changes that may trigger seizures.
Blinking content does not automatically implicate seizure-related criteria.
Related but Separate Criterion
2.3.1 Three Flashes or Below Threshold (Level A)
Applies only when content flashes at a rate or intensity that could trigger seizures.
Blinking text rarely meets this threshold and should not be treated as a seizure risk by default.
Why This Matters
Uncontrolled blinking can make content difficult to use:
- Text becomes harder to track line by line
- Attention is repeatedly pulled away from the surrounding content
- Interactive elements that blink can be harder to target or activate
This is particularly challenging for:
- Users with cognitive or attention-related disabilities
- Users with low vision or reduced visual tracking ability
- Users with limited dexterity who rely on predictable interfaces
Accessibility favours stable, predictable presentation, especially when users are reading or completing tasks.
Common Sources of Blinking Content
Blinking effects are typically introduced through:
Deprecated HTML
<p><blink>Moving Sale Thursday!</blink></p>CSS Properties
h1 {
text-decoration: blink;
}These techniques are deprecated and poorly supported across browsers. While some browsers no longer render the blinking effect, accessibility evaluation is based on user impact in real user agents, including assistive technologies, not just visual appearance in one browser.
When Blinking Becomes a Failure
Blinking content fails WCAG when all of the following are true:
- It starts automatically
- It lasts longer than five seconds
- Users cannot pause, stop, or hide it
If blinking stops within five seconds, or if a control is provided to disable it, the criterion is met.
What to Do Instead
If emphasis is needed, use static alternatives that do not rely on motion:
- Clear contrast
- Font weight or size
- Icons or labels
- Layout hierarchy
These approaches draw attention without continuously demanding it.
Who This Helps
Properly controlled content supports:
- Users with cognitive or attention-related disabilities
- Users with low vision
- Users with limited dexterity
- Screen reader users navigating structured content
Stable presentation benefits all users by improving readability and focus.
Rule Description
Blinking content that lasts more than five seconds must provide a mechanism to pause, stop, or hide the movement. Blinking is not prohibited, but uncontrolled blinking creates accessibility barriers and fails WCAG requirements.
The Algorithm
- Identify blinking or visually changing content
- Determine whether it starts automatically
- Check duration:
- If it stops within five seconds → pass
- If it lasts longer than five seconds:
- Verify users can pause, stop, or hide it
- If no control exists → the criterion fails
How to Test This
- Load the page and observe any blinking elements
- Wait longer than five seconds
- Check for controls to pause, stop, or hide the blinking
- Test with keyboard-only navigation
- Verify that assistive technologies are not forced to restart or lose context
Wrapping Up
Blinking is not automatically inaccessible, but uncontrolled blinking is. WCAG focuses on user control and predictability, not banning specific visual effects. If blinking content persists and users cannot stop it, it interferes with reading, focus, and task completion. If users must endure motion they cannot control, the design fails accessibility expectations.
Accessibility is not about removing all effects; it’s about giving users control over their experience.
