Modals are dialogues which provide information or help a user complete a task. They require the user to take an action to dismiss them.
Use a modal for self-contained processes with a clear start and end point. For the limited time frame of this action, a modal takes the user out of the current user workflow. Instead, it lets the user focus on the action and then return to the original context.
Use a modal:
- When you need to grab user’s attention for important message
- When you want to show additional information without losing the context of the parent page.
- To break down a complex workflow into simpler step
Do not use a modal:
- For nonessential information that is not related to the current workflow.
- For complex workflow that requires additional information unavailable in the modal
- Avoid modal over modal. It can confuse user about the context.
The title summarizes the purpose of the modal. In a confirmation modal, use a question in your title and make sure the action is clearly called out in the buttons.
The content may differ between different types of modals. Be concise and provide a clear explanation of the task or information a user should focus on.
Buttons should include clear and direct action for the user to take. Buttons are right-aligned based on the Z Pattern. Read more about it in Button Placement.
The background overlay is dark with opacity to provide the feeling of a third dimensional layer. This also eliminates distraction and helps the user focus on the modal content.
There are multiple sizes for modals. The Clarity modal defaults to medium but different sizes could be used based on the content and screen sizes you are planning to support. Always remember to test responsiveness as you design and use modals.
|Small Modal||Medium Modal||Large Modal||X-Large Modal|
|Width: 288px||Width: 576px||Width: 864px||Width: 1152px|
|Class: ||Default*||Class: ||Class: |
In the following example, we are using a small size modal dialog.
Modals are used in different scenarios. Most notably: alerting the user, confirmation dialogs, and task-oriented workflows.
The background overlay animates once a modal is launched to grab a user’s attention and retain their focus. Modals and backdrops support fading animations. Clarity recommends using
fadeDown on the
fade on the
modal-backdrop. These animations hide the modal and backdrop by default. Adding or removing the
in class animates the modal or backdrop in or out, respectively.
A user needs to actively dismiss a modal. A modal should not disappear on its own. Taking any of the actions to either cancel or proceed should eventually dismiss the modal.
There are multiple ways to dismiss a modal but a user needs to intentionally make that choice.
Clarity Modals are not dismissed when clicking on the background overlay. This prevents losing information or data. An option to override this is available.
Modals should not launch other modals. Stacking modals makes it hard to dismiss them and confuses the user on their levels of importance.
If you see a need to stack modals, you should:
- Seek alternatives to the second modal such as inline expansion within the first one.
- Seek alternatives to the use of modals in that scenario and explore alternatives such as inline task completion.
Scrolling makes it hard for a user to go through the content of your modal or complete the task assigned. Use scrolling only when absolutely needed.
If your modals scroll, make sure:
- You’re using the right modal size based on your content and supported screen sizes.
- Consider alternative components to using modal if the content is too long or too complex within a modal.
Besides a static HTML/CSS Modal component, we also offer a fully interactive Angular version of the component. So if you are using Angular, you can use the
ClrModal component. By using
ClrModal, you'll be able to leverage its interactive behavior and features out-of-the-box. If you would like to learn more about how to customize its default interactive behavior, please refer to the API tab.