Goal
Ensure hover/focus-triggered content is usable for keyboard and pointer users.
Success Criterion · WCAG 1.4.13
Content on Hover or Focus
Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the additional content is dismissible, hoverable, and persistent unless it is an input error or does not obscure other content.
Level AAWCAG 2.1Perceivable1.4 · Distinguishable
Copy button ready
What to do
For content that appears on hover or focus, ensure it can be dismissed, hovered, and remains visible long enough to be read.
Why it matters
Tooltips and popovers that disappear unexpectedly can block access, especially for keyboard users and people with low vision.
Success criterion
What WCAG 1.4.13 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: (1) Dismissible: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content. (2) Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing. (3) Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
Intent
Why WCAG created this requirement
- Hover-only interactions exclude keyboard-only users and can be difficult for touch and magnifier users.
- Transient tooltips can obscure content and create “chasing” behaviors.
- Users must be able to access and dismiss additional content predictably.
Benefits
Who gains when you pass
- Keyboard users can read and interact with focus-triggered content without it disappearing.
- Low vision and magnifier users can move the pointer without losing the popover.
- Users with motor impairments avoid precision hovering requirements.
- Users can dismiss obstructing overlays without losing their place.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Tooltips may disappear when users move the mouse to read them.
Popovers may obscure content with no way to close them except moving focus away.
Keyboard users may trigger content that blocks the view but cannot dismiss it.
Exception guidelines
Use the WCAG 1.4.13 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Input error messages
Additional content that communicates an input error may be exempt from dismissibility.
Requirement
Ensure error messages remain available and discoverable, and do not create traps.
Does not obscure or replace other content
If the additional content does not obscure or replace other content, dismissibility may not be required.
Requirement
Verify it truly does not obscure/replace other content.
Overview
When extra content appears on hover or focus (like tooltips, submenus, popovers), users must be able to dismiss it without moving focus/hover, move the pointer over it without it disappearing, and it must stay visible until the user dismisses it or focus/hover moves away. This prevents content from vanishing before users can read or interact with it.
- Provide an explicit close button or allow Escape to dismiss popovers/tooltips when appropriate.
- Ensure hoverable content remains visible when pointer moves onto the popup.
- Avoid popovers that cover essential content without a dismissal method.
- Input error messages are treated differently; they may be exempt from dismissible requirement in some cases.
Reference: All summaries and highlights originate from Understanding WCAG 1.4.13 and the W3C quick reference.
Fast facts
- Conformance level
- Level AA
- WCAG version introduced
- WCAG 2.1
- Principle
- Perceivable
- Guideline
- 1.4 · Distinguishable
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Tooltip
Pass
Tooltip stays visible when pointer moves onto it and can be dismissed with Escape.
Fail
Tooltip disappears as soon as the pointer leaves the trigger, preventing reading.
Popover help panel
Pass
Help popover has a close button, is hoverable, and remains until dismissed.
Fail
Help popover obscures content and can only be removed by moving focus away.
Dropdown menu
Pass
Menu remains open while pointer moves into it; keyboard users can navigate items.
Fail
Menu collapses when moving the pointer to the menu area.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document tooltip/popover interaction standards (Escape to dismiss, persistence rules).
- Capture evidence for representative components showing dismissible/hoverable/persistent behavior.
- Include guidance in component library for accessible overlays.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Understanding 1.4.13
Official W3C interpretation, techniques, and intent for Content on Hover or Focus.
Quick Reference 1.4.13
Filterable list of sufficient techniques and failures.
ARIA Practices: Tooltip Pattern
ARIA Authoring Practices tooltip pattern guidance.
ARIA Practices: Menu Button Pattern
ARIA Authoring Practices guidance for menus triggered by buttons.
Implementation checklist
Capture progress and blockers
- Inventory UI patterns that show content on hover/focus (tooltips, menus, popovers).
- Add dismissal mechanisms (Escape, close button) for overlays that obscure content.
- Ensure hover-triggered overlays are hoverable (pointer can move into them).
- Ensure overlays persist until dismissed or focus/hover is removed.
- Make sure keyboard users can reach interactive elements inside popovers when applicable.
- Prevent tooltip/popup from covering the trigger or essential nearby content.
Testing ideas
Prove conformance with evidence
- Trigger tooltips/popovers via keyboard focus and via pointer hover.
- Verify the content can be dismissed without moving focus/hover (e.g., Escape or close button).
- Move the pointer onto the popup and ensure it stays visible (hoverable).
- Verify the popup remains until dismissed or focus/hover leaves (persistent).
- Check that the popup does not trap focus and does not block the user from proceeding.
Related success criteria
More from Distinguishable (1.4)
WCAG 1.4.1Use of ColorLevel AWCAG 1.4.2Audio ControlLevel AWCAG 1.4.3Contrast (Minimum)Level AAWCAG 1.4.4Resize TextLevel AAWCAG 1.4.5Images of TextLevel AAWCAG 1.4.6Contrast (Enhanced)Level AAAWCAG 1.4.7Low or No Background AudioLevel AAAWCAG 1.4.8Visual PresentationLevel AAAWCAG 1.4.9Images of Text (No Exception)Level AAAWCAG 1.4.10ReflowLevel AAWCAG 1.4.11Non-text ContrastLevel AAWCAG 1.4.12Text SpacingLevel AA