<blink> elements must not be used
Content available in English only.
Accessibility isn't just about avoiding violations — it's about ensuring that everyone can use your product with confidence. This guide explains each rule's intent, highlights common issues, and shows how to fix them according to WCAG and the European Accessibility Act (EAA).
These guidelines do not replace the official WCAG standards. They’re concise, developer-focused notes to help you identify and fix issues effectively.
<blink> is deprecated and inaccessible—never use it.
Overview
Why this matters
Uncontrolled blinking and moving content can distract users and make content hard to read or operate. If users cannot pause or stop the behavior, core tasks may become inaccessible.
How to fix this issue
Remove deprecated blinking patterns and replace with static content, controlled animation, or user-triggered updates. For auto-updating or moving content, provide pause, stop, or hide controls and keyboard access to those controls.
Developer Guidance
Enforce a no-`blink` and no-uncontrolled-motion rule in linting and component review. For any moving or auto-updating UI, implement explicit pause or stop controls and keyboard access to them. Respect reduced-motion preferences and use semantic announcement patterns (`aria-live`) for status updates instead of visual blinking.
Code Examples
Incorrect Implementation
<blink>New updates available</blink>Correct Implementation
<p role="status" aria-live="polite">New updates available</p>Real-World Implementation
Before
<div class="alert">
<span class="blink">Payment failed</span>
</div>
<!-- Blinking loops continuously with no user control -->After
<div class="alert" role="status" aria-live="polite">
Payment failed
</div>
<button type="button" aria-controls="ticker" aria-pressed="false">Pause updates</button>Manual Testing
- 1. Identify moving, blinking, scrolling, or auto-updating regions.
- 2. Verify users can pause, stop, or hide each non-essential moving region.
- 3. Confirm controls are keyboard reachable and clearly labeled.
- 4. Test with reduced-motion preferences enabled and confirm behavior is reduced or controlled.
- 5. Validate announcement behavior with screen reader for status updates using semantic live regions.
Related Operable Rules
Trusted by organizations across Europe working toward WCAG and EAA conformance