Coach mark
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.


Anatomy#

Options#
Usage guidelines#
Use a consistent width#
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 each one.




Keep titles concise#
Aim for concise titles, and keep complex information in the body text. Titles should be in sentence case. Avoid wrapping if possible.




Keep body text succinct and informative#
Coach marks are meant to be quick overviews of functionality. Body text 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. View the




Align coach marks with the action being explained#
Coach marks are aligned with their related components in the same way as




Don't obscure a relevant part of the UI with the coach mark.
Use an indicator to show the source#
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.




Using the "Skip tour" button#
The “Skip tour” button should always be a quiet secondary button, even when it’s the only button available in the dialog. Omit this button on the last step of a tour.




Don't use inconsistent action names within 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.




Allow dismissal when a coach mark depends on an action#
When a coach mark is dependent on a user action, it’s OK to remove the primary action button as long as the user still has a way to exit.
On a one-off coach mark, this means that the primary action button should remain as a way to dismiss. In a tour, it’s acceptable to show only the "Skip tour" button.




Don't require users to confirm that they've taken an action#
When a coach mark is dependent on a user action, don't force the user to confirm that they've taken that action.


Internationalization#
Keyboard interactions#
Changelog#
- Updated all colors to 6.0.0
- Increased opacity of the animated indicator
- Added text overflow behavior
- This component is now individually versioned (individual versions of existing components start at 5.0.0)
- Added RTL (right-to-left) guidelines
Design checklist#

All interactive states
Includes all interactive states that are applicable (hover, down, focus, keyboard focus, disabled).

All color themes
Works properly across all four color themes (lightest, light, dark, darkest).

All platform scales
Includes a desktop scale (UWP, macOS, web desktop) and a mobile scale (iOS, Android, web mobile).

Accessible use of color
Color is not used as the only visual means of conveying information (WCAG 2.0 1.4.1).

Accessible contrast for text
Text has a contrast ratio of at least 4.5:1 for small text and at least 3:1 for large text (WCAG 2.0 1.4.3).

Accessible contrast for UI components
Visual information required to identify components and states (except inactive components) has a contrast ratio of at least 3:1 (WCAG 2.1 1.4.11).

Content design
UI language and information design considerations have been incorporated into component design.

Defined options
Includes relevant options (variant, style, size, orientation, optional iconography, decorations, selection, error state, etc.)

Defined behaviors
Includes guidelines for keyboard focus, layout (wrapping, truncation, overflow), animation, interactions, etc.

Usage guidelines
Includes a list of dos and don'ts that highlight best practices and common mistakes.

Writing guidelines
Includes content standards or usage guidelines for how to write or format in-product content for the component.

Internationalization guidelines
Works properly across various locales and includes guidelines for bi-directionality (RTL).

Keyboard interactions
Follows WCAG 2.0 standards for keyboard accessibility guidelines and includes a description of the keyboard interactions.

Design tokens
All design attributes (color, typography, layout, animation, etc.) are available as design tokens.
UI kit
Includes a downloadable XD file that shows multiple options, states, color themes, and platform scales.

Generated UI kit
Includes a downloadable XD file, generated by code using design tokens defined in Spectrum DNA, and shows multiple options, states, color themes, and platform scales.

In Spectrum for Adobe XD plugin
Component is included in the Spectrum for Adobe XD plugin.