Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing templates, rendered HTML, or shared components related to Create accessible tooltips. Validate the final browser-facing markup, not just the source framework abstraction.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | -28% | 0% |
| case-02 | ✓→✓ | = Same ✓ | -12% | 0% |
| case-03 | ✓→✓ | = Same ✓ | -12% | 0% |
| case-01 | ✓→✓ | = Same ✓ | -18% | 0% |
| case-05 | ✓→✓ | = Same ✓ | -28% | 0% |
Inaccessible tooltips leave keyboard and screen reader users without important contextual information, creating an unequal experience and potential confusion.
Verify tooltips are keyboard accessible, use appropriate ARIA roles (tooltip), and can be dismissed without moving focus.
Implement tooltips with role='tooltip', aria-describedby, keyboard triggering, and Escape key dismissal.
Explain the accessibility requirements for tooltips including keyboard access, ARIA attributes, and timing considerations.
Review templates, server-rendered HTML, and shared components that output markup related to Create accessible tooltips. Flag exact elements, attributes, and routes where the rendered HTML violates the rule.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/html/accessible-tooltips
Other measured skills in the registry, with their headline benchmark lift.