tooltipslisted
Install: claude install-skill mgifford/accessibility-skills
# Tooltips Accessibility Skill
> **Canonical source**: `examples/TOOLTIP_ACCESSIBILITY_BEST_PRACTICES.md` in `mgifford/ACCESSIBILITY.md`
> This skill is derived from that file. When in doubt, the example is authoritative.
Apply these rules when implementing or reviewing tooltip components.
**Only load this skill if the project contains tooltips.**
---
## Core Mandate
Tooltips must convey supplementary information to all users regardless of input
method. A tooltip unreachable by keyboard is an accessibility barrier.
Tooltips are **non-interactive supplementary labels only**. If the content is
essential, or contains links/buttons, use persistent text or a popover instead.
---
## Severity Scale (this skill)
| Level | Meaning |
| --- | --- |
| **Critical** | Tooltip contains essential information with no other access route |
| **Serious** | Tooltip unreachable by keyboard or AT |
| **Moderate** | Tooltip accessible but WCAG 1.4.13 requirements not fully met |
| **Minor** | Best-practice gap; marginal impact |
---
## Critical: Essential Information Must Not Live Only in a Tooltip
A tooltip is supplementary by definition. If the information it contains is
required to complete a task, it must also appear as persistent visible text.
**Hiding essential content behind hover/focus only is Critical.**
---
## Serious: Tooltips Must Appear on Both Hover and Focus
A tooltip that only appears on hover is **Serious** — keyboard users cannot
trigger it.
```js
function showToolt