1. Identify the help and its purpose
List the controls that reveal extra information and record what the extra text explains. Distinguish optional clarification from instructions required to complete a task. Consider moving essential instructions into the normal page flow so they are available before an error or a difficult hover interaction.
WCAG 2.2 criterion 1.4.13 requires qualifying hover/focus content to be dismissible, hoverable, and persistent, subject to exceptions. Check its scope against your component.
Sources: [1]
2. Check keyboard and pointer access
Approach the trigger with a keyboard and with a pointer, then record what appears and where focus remains. Check whether the help is associated with the control it explains and whether it duplicates or obscures a useful label. A picture of the open popup does not show how a reader reaches it.
W3C’s APG tooltip pattern is explicitly a work in progress without task-force consensus. It describes focus remaining on the trigger and an aria-describedby relationship. Treat those details as provisional guidance. A popup containing focusable controls needs a different interaction pattern from the tooltip described there.
Sources: [2]
3. Move the pointer onto the help
WCAG’s hoverable condition requires content opened by pointer hover to remain visible when the pointer moves onto it. Test the actual path, including any gap.
Repeat the check when the help appears near a viewport edge or contains a longer explanation. Observe whether its position changes unexpectedly while you try to reach it. Record a reproducible sequence for a disappearing popup, including the trigger, direction of movement, and relevant viewport rather than reporting only that hover seems unreliable.
Sources: [1]
4. Check dismissal and persistence
WCAG’s dismissal condition has exceptions for input errors or content that does not obscure or replace other content. Its persistence condition keeps the help visible until the trigger is removed, the user dismisses it, or the information becomes invalid. Browser-controlled presentation unmodified by the author is excepted from the criterion.
Test the supported close action without moving away from the task, and leave the help open long enough to read it. The provisional APG tooltip pattern describes Escape dismissal. Record any timeout or repeated reopening that interferes with reading. The native browser-tooltip exception is not a general recommendation to hide essential instructions in a title attribute.
5. Check touch, zoom, and the complete task
Review how the same explanation is reached on touch devices and at increased zoom. Look for overlap with the control, clipped content, and a missing alternative where hover is unavailable. Keep the help text concise, but do not remove necessary context merely to make a cramped popup appear tidy.
Save the page version, trigger method, actual behavior, and environments checked. Classify a content problem separately from a focus or pointer problem so the right part can be fixed. Record the provisional status of any APG tooltip guidance used. This review does not certify the page or claim that a particular tooltip has been tested.
Your quick checklist
- Essential instructions are available through a dependable route.
- Keyboard and pointer triggers are checked.
- Pointer movement onto the help is tested.
- Dismissal, persistence, and applicable exceptions are considered.
- Touch, zoom, and the provisional APG status are documented.
Sources & scope
W3C supports the criterion scope and exceptions; its separate tooltip pattern remains provisional. The inventory and test record are ATN editorial guidance. No live tooltip or assistive-technology behavior was tested, and this article does not establish conformance.
- W3C WCAG 2.2: Understanding content on hover or focus (opens in a new tab)Source checked October 10, 2026
- W3C ARIA Authoring Practices: Provisional tooltip pattern (opens in a new tab)Source checked October 10, 2026
Published October 10, 2026. No affiliate links or paid placements in this guide.
