Coach marks are temporary messages that educate users through new or unfamiliar product experiences. They can be chained into a sequence to form a tour.
Coach marks are in a tour when the primary action of one coach mark will lead to the display of another. The Skip tour button creates an escape path for the user to avoid having to click through each step. A step indicator is optional but encouraged. Display of progress should be consistent throughout the tour — either all steps should have this, or none.
Coach marks can contain images that relate to their content, such as demonstrations of gestures, the UI being used, or illustrations.
Coach marks in a tour can be dependent on an action. Unless the tour is skipped, they will persist until the user takes the corresponding action, such as “open the Library panel.”
The coach mark indicator comes in standard (large) and quiet (small), with a light, dark, and blue variant for contrast in different situations.
When the title and body text are too long for the available horizontal space, they wrap to form another line. The steps are always shown in full and never wrap or truncate.
Choose a width for your coach marks that is spacious enough to accommodate all of your content. Within a tour that includes many coach marks, keep the width consistent across every instance.
Aim for concise titles, and keep complex information in the body text. They should be in sentence case. Avoid wrapping titles if possible.
Coach marks are meant to be quick overviews of functionality. Content should be at least a few words, but no more than a few sentences.
Coach mark copy should be concise, but written in complete sentences and expressing encouragement and usefulness. For more information on tone, see our voice and tone guidelines.
Coach marks are aligned with their related components in the same way as popovers. Choose a placement that keeps the related component visible on screen.
Don't obscure a relevant part of the UI with the coach mark.
Unlike popovers, the UI component a coach mark refers to does not need to take a down state. Use the placement of the coach mark and its indicator atop the component to indicate source.
The “Skip tour” button should always be a quiet secondary button, even when it’s the only button available in the dialog. Omit the “Skip tour” button on the last step of a tour.
The primary action should be brief and consistent. Use "OK" for a single coach mark. Within a tour, use “Next” for all but the last step, and “Finish” for the last step. Don’t use different primary action names for every step in a tour.
When a part of the tour is dependent on an action being taken by the user, it’s okay to remove the primary button, as long as the user has a way to exit the coach process. On a one-off coach mark, this means the primary button should remain as a route to dismiss. On a tour, it’s acceptable to preserve only the "Skip tour" button.
When part of the tour is dependent on a user action, don't force users to confirm that they've taken that action.
For RTL (right-to-left) languages, the default layout of the coach mark is mirrored. Text is right-aligned while the chevron and the button group are left-aligned.
|Tab||Moves focus to the next button inside the popover (last becomes first).|
|Esc||Exits the current coach mark. If in a tour, proceeds to the next coach mark (does not skip the entire tour).|
|Sep 11, 2019||5.1.1|
|Aug 22, 2019||5.1.0|
|Apr 18, 2019||5.0.0|
Includes all interactive states that are applicable (hover, down, focus, keyboard focus, disabled).
Includes relevant options (variant, style, size, orientation, optional iconography, decorations, selection, error state, etc.)
Works properly across all four color themes (lightest, light, dark, darkest).
Includes a desktop scale (UWP, macOS, web desktop) and a mobile scale (iOS, Android, web mobile).
Includes guidelines for layout (wrapping, truncation, overflow), animation, interactions, etc.
Includes a list of dos and don’ts that highlight best practices and common mistakes.
Follows WCAG 2.0 standards for contrast (AA).
Works properly across various locales and includes guidelines for bi-directionality (RTL).
Follows WCAG 2.0 standards for keyboard accessibility guidelines and includes a description of the keyboard interactions.
Includes a downloadable XD file that has been generated by code and shows multiple variations, states, color themes, and scales.
All design attributes (color, typography, layout, animation, etc.) are included in Spectrum DNA.