Tooltips are floating labels to describe or add additional information when users hover over, focus on, or click an interactive element. Use sparingly.
- Autocomplete (not built)
- Button Group (not built)
- Checkbox Field
- Checkbox Group
- Date Picker (not built)
- Empty State
- Filter Drawer
- Global Notification
- Guidance Block
- Hero Card
- Icon Button
- Infinite Scroll (not built)
- Inline Notification
- Likert Scale Legacy
- Loading Placeholder
- Loading Skeleton (not built)
- Loading Spinner
- Pagination (not built)
- Progress Bar (not built)
- Progress Stepper
- Radio Group
- Search Field (not built)
- Slider (not built)
- Split Button
- Text Area Field
- Text Field
- Tile Grid
- Toast Notification
- Toggle Switch
- Tooltips are used to provide additional information when space is tight.
- Tooltips should be concise but can be rendered with one or more lines of text.
- Tooltips must be accessible via hover, focus or click.
- Trigger tooltips from Interactive elements (Buttons, Links, Icon buttons) or Non-interactive elements (Icons, Abbreviations, Truncated text)—be mindful of keyboard accessibility
- Use sparingly. Tooltips innately hide information. Consider exposing it immediately without a tooltip or removing it completely.
Use sparingly. Tooltips innately hide information. Consider exposing the information immediately without a tooltip or removing it completely.
- The anatomy of a tooltip is made up of a container, description and tip (i.e. arrow).
- A tooltip is connected to a trigger element, such as a button or icon, that shows the tooltip when the interactive trigger element is hovered, focused, or clicked. (More details below.)
- Text and tips within tooltips can be left, centered and right aligned, as appropriate within its environmental context.
- Use strong signifiers for trigger elements to ensure the tooltip is discoverable.
- The proximity of tooltips is always paired nearby the element with which they are associated.
- Don’t crop tooltips e.g. at the edge of modals.
- Needs to be discoverable:
- E.g. something like an icon to tell you there’s a tooltip
- E.g. show the first tooltip/popover immediately on page load so people know they’re there
- Avoid triggering tooltips from text without indicators that the text has behaviour
- Needs to not be noisy (e.g. we don’t litter UI with icons all the time)
- Only trigger tooltips from:
- Interactive elements:
- Icon buttons
- Non-interactive elements (be mindful of keyboard accessibility):
- Abbreviations (e.g. dashed underlined text for HRIS that shows a tooltip that says Human Resource Information System)
- Truncated text
- Interactive elements:
- For interactive elements that trigger tooltips, only have optional information in the tooltip because it could be missed when the user clicks.
For context, see Moods.
- When combined with an icon, use the matching icon and mood (Positive, Informative, Cautionary, Negative). For example, when using a Cluny (blue) colored information icon, show an informative tooltip.
- When used without an icon, use the Default tooltip (white).
- A Tooltip lifts up from the trigger point, by “slide fading” towards the top of the screen away from the trigger point. Related: Tooltip arrows always point down and “slide fade” upwards unless they're at a viewport edge, then the tooltip should move in the opposite (and most logical) direction.
- Use sparingly. If you’re building something that requires a lot of tooltips, work on clarifying the design and the language in the experience.
- Only show 1 tooltip at a time.
- Tooltips contain limited content so we can use an ‘announcer’ to announce tooltip content to people using screen readers e.g. using an ARIA live region.
- In contrast, a user might interact with a Popover, requiring focus, so we need to move focus to the Popover when it’s triggered and support keyboard navigation to dismiss a dismissible Popover.
Tooltips are a useful way to highlight additional information for a feature or element in the platform. Use them sparingly and keep these rules in mind:
Tooltips should never stop a user (or be a gate) from completing a task or performing an action. They disappear so they should never contain critical information that a user would absolutely need to proceed, or information without which a user may cause errors. If the information is crucial for a user to proceed, consider using a modal or inline notification instead.
Never include any kind of error messages in a tooltip. As tooltips are hidden, a user may not be aware of an error if it exists in the tooltip text.
Good tooltips contain concise and helpful information. Keep it to one or two very short sentences. Don’t use it to duplicate information that already exists on the page. Instead, closely consider its placement and whether the disclosed copy will inform the action the user is about to perform.
As tooltips only surface from a hover, never include links or buttons in the copy. If your tooltip requires either of these, considers putting your content in a popover.
All tooltips copy should be in sentence case i.e. the first letter of the first word is capitalized and everything else is in lower case unless it’s a proper noun or feature name. Always err on the side of minimal punctuation, so leave out full stops and commas where possible.
- Use when the description content would be too much information to include inline or create too much clutter. For example, when expert users have seen it many times.
- Use for icon-only buttons or for a button with an associated keyboard shortcut.
- Don’t use tooltips to restate visible UI text.
- If you need lots of tooltips and icons to trigger them, consider an onboarding pattern instead, such as coachmarks.
- To communicate critical information, including errors in forms or other interaction feedback. Consider using Modals or Notifications
- Not contain any links or buttons. Consider using a Popover.
On this page
- To keep in mind
- Copy guidelines
- When to use and when not to use
- See also
- External links