AI Tooltip Copy Generator

Use tooltips for icon-only buttons that need text labels, features whose purpose is not immediately obvious, settings or options that need brief clarification, and data points that need context (like dashboard metrics). Do not use tooltips for essential information that all users need — that should be visible text. Tooltips are supplementary help, not a replacement for clear interface design.

Tooltip text should be scannable in 1-2 seconds — typically 5 to 15 words. For simple explanations, one short sentence is ideal. If you need more than two sentences, consider using a help popover or inline help text instead. The constraint forces clarity: if you cannot explain something in 15 words, the feature itself may need a clearer name or better design.

Hover-triggered tooltips work well for desktop users but are inaccessible on touch devices. Best practice is to trigger on hover for mouse users, on focus for keyboard users, and on tap for mobile users. For complex tooltips with links or multiple pieces of information, use a click-triggered popover instead, as hover content disappears when the cursor moves away.

Use the aria-describedby attribute to associate tooltip text with its trigger element. Ensure tooltips appear on keyboard focus (not just hover). Keep tooltip text in the DOM (not just visual) so screen readers can access it. Avoid putting essential actions or links inside tooltips — they should be supplementary. Follow WCAG 1.4.13 for dismissible, hoverable, and persistent content requirements.

Every icon-only button should have either a visible text label or a tooltip — icons alone are ambiguous even for common actions. Universally recognized icons (search magnifying glass, close X, home) may not need tooltips if they include proper aria-labels. For custom or uncommon icons, always add a tooltip. When in doubt, test with users: if anyone hesitates, add a tooltip.