Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for tooltips. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-05 | ✓→✗ | ▼ Worse | 15% | 0% |
| case-09 | ✓→✓ | ＝ Same ✓ | -1% | 0% |
| case-02 | ✓→✓ | ＝ Same ✓ | 9% | 0% |
| case-03 | ✓→✓ | ＝ Same ✓ | -11% | 0% |
| case-04 | ✓→✓ | ＝ Same ✓ | 10% | 0% |
Tooltips often contain essential information; if they aren't properly named or associated with an element, that information remains hidden from screen reader users.
aria-describedbyVerify that all elements with role="tooltip" have an accessible name or are linked to a trigger element via aria-describedby.
Assign an accessible name to the tooltip or ensure it is correctly referenced by the element it describes.
Explain how to correctly associate tooltips with triggers so that screen readers announce the extra information.
Review the rendered markup and interactive states that affect Provide accessible names for tooltips. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/accessibility/aria-tooltip-name
Other measured skills in the registry, with their headline benchmark lift.