spec 2 linked patterns checked
ARIA tooltip role
Documents tooltip role behavior, aria-describedby ownership, automatic focus or hover display, Escape dismissal, non-focusable tooltip content, and why tooltips cannot contain interactive elements.
Read with a purpose
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Tooltip | Choose tooltip when the target already has a usable name and needs only a short supplemental description on focus or hover. | The owning element keeps focus while the tooltip is visible. | Supports aria-describedby ownership, automatic display, and the no-interactive-content boundary. |
| Tooltip-only required information | Flag this anti-pattern when the tooltip content is necessary to complete the task correctly or avoid a harmful outcome. | Users can complete the task without reading a tooltip. | Supports the tooltip boundary as noninteractive described content, not a container for required task controls or long instructions. |
Comparisons supported by this source
- Tooltip vs popover vs inline message vs icon-only ambiguous action
MDN supports aria-describedby ownership and the no-interactive-content boundary.
- Tooltip-only required information vs tooltip vs inline message vs disclosure details vs popover
Supports aria-describedby tooltip ownership, automatic display, and the no-focusable-content boundary.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: MDN Web Docs. Last checked: .