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.
58
67%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/aria-tooltip-name/SKILL.mdTooltips 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
48405aa
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.