Short description

Dialogues contain a headline, text and UI controls. They retain focus an required action has been taken. Use dialogues sparingly because they are interruptive to the user. 

When and how to use it

Use a dialogue when confirmation is needed. For example when deleting an account or removing a an item that is needed for something else not visible in this view.

They may also be used as a guide when an error has occurred that has a known way of handling the problem, for example when logging in.

Behaviour

Can not be dismissed by clicking outside - the user is "forced" to take action. The content behind the overlay is locked and can not be scrolled.

The action of the primary button should confirm the user action that triggered the dialogue. Even if we suspect that the user do not understand that. For example, when a user is choosing an action that will delete an account and we want to verify that the user really want to do that, the primary button should be “Delete” (action), not “Cancel” (back away).

The dialogue is often used to confirm an action that the user took, that could lead to a negative consequence, therefore:

• The title should be a statement referring to the action that will happen.
• The text in the dialogue should explain the action and its consequences.
• You may use an emphasized sentence in the message, but don't overuse it, and avoid please.
• The title of the dialogue should match the primary button. Avoid Yes, No, and Ok in the answer/buttons.
• The primary and secondary buttons must not be too similar. Don't make the user think about what button to click. Use Back instead of Close as the abort action if the primary action is Cancel.
• Also, put the action that the user made in the primary button. We might want the user to take another action, but that was the action they took. On purpose, or not.

Do's and don'ts

Do this

Don't do this

-

• Details: Specification in Figma
• Instruction: How to access Figma