Skip to end of banner
Go to start of banner

Tooltips

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 25 Next »

ONGOING Description

Tooltips are small text like bubbles that appear when the user hovers an element.

(warning) For the purpose of this document, tooltips and infotips are the same 

Usage & Behaviour

General guidelines

Content

  • Most tooltips contain plain text which usually describes the control/object they point to.
  • Content cal also be tooltips with header, icons, dynamic content, actionable buttons, links, tables Etc... 

Examples:

ComponentRegular size
Regular

Regular with heading

Error

see Field Validation

Warning

see Field Validation

Informative

Help
Additional examples (from different apps)
Regular with dynamic content (Calendar | statistics)

Regular with heading - 2 lines (Calendar)



Regular with structured content (Queue Analytics, Forecast)
Regular with actions(e.g. buttons)

Text

  • When the tooltip is applied to buttons, use user action-oriented copy that communicates the value in a straight forward manner
  • Keep it short. If you reach more than 150 chars reconsider the tooltip and use a pop-over <<TBD link to LUX pages>>

See examples in table

Target areaCorrectIncorrect

Ribbon button

"Generate a schedule for selected employees"

Rationale: explaining the main operation of the button including who it works on

"Generate schedule"

Rationale: repeating the same text as the button is redundant

Search field

"Search within the listed tree of organisation"


Rationale: explaining the main operation of the field including who it works on

"will search upon all trees of organisation excluding  the dates or any other non-organisation relevant information. "

Rationale: Too long, and using unnecessary information which can be understood from context of the field and screen

Format

Preferred usage for tooltip is with a small "triangle" at the outline to point mouse cursor (when technically feasible). 

Triangle position should be dynamic and point the location of the tooltip in relation to the mouse cursor and screen edges/limitations. 

See examples:

Placement or Positioning

  • Position of tooltip should be where mouse cursor last position see Interaction section
  • Avoid using the tooltip covering an element the user will interact with.
    For example:


  • Avoid using the tooltip on top of another element when items seemed to be arranged as groups 

Interaction

Tooltip presentation

The following steps describe how should the tooltip be presented according to user behavior and context

Regular (e.g. truncation of any sort):

  1. Mouse cursor enters target area: display visual feedback of hover within 0.1 seconds..
  2. If cursor remains stationary within target area for 1.5 seconds,
    1. Display tooltip on location of the cursor currently within target area (position of tooltip doesn't change while cursor is inside target area)
  3. If cursor had moved to another target area in less than 1 second, remove current tooltip and show tooltip for new target after 0.1 seconds
  4. Keep displaying the exposed content element until the cursor has left the target area or 12 seconds had passed
    1. Once the cursor left the target area close the tooltip after 0.1 seconds 

Graph or micro chart

Usually require more quick response presenting information. See example below.

  1. Mouse cursor enters target area: display visual feedback of hover within 0.1 seconds..
  2. If cursor remains stationary within target area for 0.2 seconds
  3. <<Continue as regular or tooltip>>

Tooltips with action

Follow the same Regular tooltip interaction with the following changes

  1. While the mouse cursor is on the target area OR tooltip area, keep displaying the tooltip
  2. Once the cursor left the target AND tooltip area, close the tooltip after 1 seconds

Target area

Target area should include all elements to which the tooltip is pointing.
The following example is an incorrect behavior where different parts of the target area are treated as internal target area

General

  • Tooltips on graphs may sometimes add additional graphical elements to help the user focus on the visual.
    See example in Queue Analytics where a vertical line is added with tooltip to help maintain focus of hour:


  • Using "Esc" on the keyboard should hide the tooltip while the mouse cursor is still within the target area. Getting out of the target area, should reset the interaction as explained above.

Best practices

  • Tooltips should not be used as the only way to accomplish a task (should not be vital for the task)
  • Tooltips with obvious/redundant text are not beneficial to the user
    <<TBD update image>>

  • A formatted structure is easier to read than big chunk (see in additional examples under Content)

Accessibility compliance

Focus management

We already set a general guidelines described in /wiki/spaces/UX/pages/308969693

Focusing on an element with tooltip should

Screen reader support 

Should be done automatically by the screen reader.

Contrast & size compliance

Complied by design

Design




  • No labels