Guidelines and checklist for tooltips (Windows Store apps)
Follow these guidelines for adding tooltip controls to your Windows Store app.
A tooltip is a short description that is linked to another control or object. Tooltips help users understand unfamiliar objects that aren't described directly in the UI. They display automatically when the user presses and holds, or hovers the mouse pointer over a control. The tooltip disappears when the user moves the finger, the mouse pointer, or a pen pointer.
Use a tooltip to reveal more info about a control before asking the user to perform an action. You can also use a tooltip to show the item under the finger during touchdown, so that users know where they are touching. (You should try to find other ways to disambiguate first, such as use a larger control, more spacing, or styling the control's active/hover state.)
When should you use a tooltip? To decide, consider these questions:
- Is the info displayed based on pointer hover?
If not, use another control. Display tooltips only as the result of user interaction—never display them on their own.
- Does a control have a text label?
If not, use a tooltip to provide the label. It is a good programming practice to label most controls and for these you don't need tooltips. Toolbar controls and command buttons with graphic labels need tooltips.
- Does an object benefit from a more detailed description or further info?
If so, use a tooltip. But the text must be supplemental—that is, not essential to the primary tasks. If it is essential, put it directly in the UI so that users don't have to discover or hunt for it.
- Is the supplemental info an error, warning, or status?
If so, use another UI element, such as a flyout.
- Do users need to interact with the tip?
If so, use another control. Users can't interact with tooltips because moving the mouse makes them disappear.
- Do users need to print the supplemental info?
If so, use another control.
- Will users find the tips annoying or distracting?
If so, consider using another solution—including doing nothing at all. If you do use tips where they might be distracting, allow users to turn them off.
Here are some examples of good ways to use tooltips:
- Showing the day of the week when users touch a date in a calendar.
- Showing a preview of the linked website when users touch a hyperlink.
|Do||Keep the tooltip text concise. Tooltips are perfect for short sentences and sentence fragments. Large blocks of text are difficult to read and overwhelming.|
|Create helpful, supplemental tooltip text. Tooltip text must be informative. Don't make it obvious or just repeat what is already on the screen. Because tooltip text isn't always visible, it should be supplemental info that users don't have to read. Communicate important info using self-explanatory control labels or in-place supplemental text.|
|Use images when appropriate. Sometimes it's better to use an image in a tooltip. For example, when the user touches a hyperlink, you can use a tooltip to show a preview of the linked page.|
|Don't||Don't use a tooltip to display text already visible in the UI. For example, don't put a tooltip on a button that shows the same text of the button unless touching the button blocks its text.|
|Don't put interactive controls inside the tooltip.|
|Don't put images that look like they are interactive inside the tooltip.|
- Roadmap for Windows Runtime apps using C# or Visual Basic
- Roadmap for Windows Runtime apps using C++