The <marquee> element creates automatically scrolling content that moves across the screen without user interaction. While this behaviour may appear decorative, auto-scrolling content can interfere with reading, interaction, and focus, especially when users cannot pause or stop it.
The <marquee> element is deprecated in HTML and should not be used in modern web content. More importantly, marquee-based content typically introduces moving content without user control, which is where accessibility failures occur.
This criterion is not about deprecated code alone. Accessibility failures occur when scrolling content moves automatically, and users cannot pause, stop, or hide it.
WCAG Success Criterion
2.2.2 Pause, Stop, Hide (Level A)
For 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 the movement is essential.
Most <marquee> implementations fail this criterion because they scroll automatically and provide no mechanism for user control.
Why This Matters
Automatically scrolling content introduces several barriers:
- Text that moves continuously is harder to read and track
- Links or controls inside moving regions are difficult to activate
- Motion competes with surrounding content for attention
This particularly affects:
- People with low vision, who may struggle to track moving text
- People with cognitive or attention-related disabilities, for whom motion can be distracting
- Users with limited dexterity, who may not be able to click moving links accurately
- Screen reader users, who may experience interruptions or inconsistent announcements
Accessibility prioritises user control and predictability, especially for content that moves.
Example of the Issue
Deprecated HTML with Auto-Scrolling Content
<marquee behavior="scroll" direction="left">
Frisbeetarianism is the belief that when you die, your soul goes up on the roof and gets stuck.
</marquee>This content:
- Starts moving automatically
- Continues indefinitely
- Cannot be paused, stopped, or hidden by the user
As a result, it fails SC 2.2.2 Pause, Stop, Hide.
Common Misconception
“Marquee elements fail accessibility because they are deprecated.”
Deprecation alone does not cause a WCAG failure. The failure occurs because marquee content moves automatically without user control. Any technology like HTML, CSS, or JavaScript that creates uncontrolled scrolling content can fail this criterion.
Rule Description
Content that scrolls automatically must provide users with a way to pause, stop, or hide the movement. The <marquee> element almost always violates this requirement and should be removed or replaced with a static or user-controlled alternative.
The Algorithm
- Identify scrolling or moving content that starts automatically
- Check whether the movement lasts more than five seconds
- Verify whether users can pause, stop, or hide the movement
- If no control is provided, the criterion fails
How to Fix the Problem
- Remove
<marquee>elements entirely - Replace scrolling text with static content
- If movement is necessary, provide clear controls to pause, stop, or hide it
- Prefer CSS and JavaScript solutions that respect user control and accessibility requirements
Wrapping Up
The problem with <marquee> is not that it is old; it is that it removes control from users. Moving content is only accessible when users can stop it. If text scrolls automatically and cannot be paused, it creates barriers for reading, interaction, and comprehension.
When in doubt, choose static, predictable presentation over motion.
