liveBook · Manning

Content on hover or focus

As explained in Architecting Accessibility

Content on Hover or Focus is a WCAG success criterion requiring additional content shown on hover or focus to be dismissible, hoverable, and persistent.

Supplementary help should remain usable for people who need to move a pointer onto it or navigate with a keyboard. Custom tooltips and similar content must be dismissible, hoverable, persistent, and keyboard accessible—not dependent on hover alone. section 6.6

For a tooltip or similar content:

  • Allow dismissal without moving the pointer or keyboard focus; Escape is one example. section 6.6
  • Let users move the pointer onto the content without making it disappear. section 6.6
  • Keep it visible until dismissed, the pointer or focus moves away, or the information is no longer valid. section 6.6
Figure 6.15 Tooltip control, showing supplementary information about an input field using an icon button trigger.

The tooltip example uses an icon button to reveal supplementary information about an input field. section 6.6

The HTML Popover API’s popover="hint" provides some behavior, including Escape dismissal; other requirements still need appropriate handling. section 6.6

How Architecting Accessibility covers it

How deep it goes
Defines dismissal, hoverability, persistence, and keyboard access, while noting the Popover API handles only some behavior.
Examples
Shows an icon-button tooltip for input-field help and Escape dismissal.
What you can do after
Apply the HTML Popover API’s popover="hint" for some tooltip behaviors and handle the remaining requirements appropriately.
How it connects
Connects tooltips and the HTML Popover API with WCAG 2.2 Success Criterion 1.4.13.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting Accessibility. The section links point to the parts of the book it draws on.