WCAG 2.1 · Level AA · Perceivable
1.4.13 Content on Hover or Focus
Manual verification
How to validate 1.4.13 by hand
Check additional content shown on hover or keyboard focus, such as tooltips, menus, and popovers.
Start with the extension result
Reopen the reported URL and reproduce the same state (for example, after expanding a menu or submitting a form). Use the result’s Highlight action when available, or its affected-element details and CSS selector, to find the reported content. Apply the checks below to that content and its context. If the element or state has changed, rescan and record that difference before deciding whether the finding still applies.
- Reveal the content with a pointer and with keyboard focus; confirm it appears for both when the trigger supports both.
- Move the pointer into the added content and press Escape; verify it can be dismissed without moving focus unless it communicates an input error.
- Keep the content open while moving between trigger and popup, and check that it remains visible until dismissed or no longer relevant.
Evidence to record
Record how the content appears, whether it overlays or replaces content, and which of dismissible, hoverable, or persistent behaviors fail.
Scope and exceptions
Browser-native content and certain content that does not obscure or replace other content have exceptions. Evaluate each required behavior for the actual popup.
Record the review outcome
- Confirmed: the recorded evidence shows the requirement is not met in the tested page state, and no applicable exception explains it.
- Not reproduced: the reported issue is absent in the current state. Record the URL, state, and affected element you checked; this does not prove other pages or states conform.
- Needs more review: evidence is incomplete, the content requires human judgment, or an exception is uncertain. Record what remains to be checked instead of treating it as a pass.