The last version of Internet Explorer, version 11, was released on October 17, 2013. This is a very long time ago when taking into account the rapid development of web technologies. These days it is often difficult and time consuming to get modern technologies to work well in this old browser. More and more frameworks are dropping support, and even Microsoft themselves has announced that they will fully drop support for IE in their own services in 2021.
Consequently, we have decided to not include support for IE in the Design Library website.
Coach marks are contextual tips in an interface.
Coach marks are contextual tips that focus' on making the user aware of a new feature, the benefits of an existing one or a moved feature within an interface.
Coach marks are used when we want the user to be aware of a new feature or a change within an interface. It should help the user understand the context of the feature we are hinting about by pointing to where it can be found in the interface.
We use coach marks only when it feels necessary. Coach marks can help on how to interact within an interface but on the other hand, they cannot save a poor design, so it is better to prevent the need for usage in the first place or incorporate them very wisely.
Common use cases for coach marks:
Coach marks highlight only a certain part of an interface, the part of the interface that holds the feature that is in focus.
Coach marks follow a popover style, meaning they display content in a small modal. User can interact with the coach mark, including clicking links/buttons to either read more or dismiss the message.
Place the coach mark next to what it is referring to and point directly to the feature with the pointer/caret
The coach mark takes tab order one. After being dismissed the user end up on original tab object number one on the screen, (could be a skip link).
The coach mark need to trap the user inside the modal using a focus trap so It’s not possible to tab to objects on other places in the interface until the coach mark is actively dismissed by the user.
Use an alert role or an dialogue role to make sure that the screen reader catches that the message is visible on the screen and reads it before other objects.