Use the status component when it’s possible for something to have more than one status and it’s useful for the user to know about that status. For example, you can use a status to show whether an item in a list has been ‘completed’.
WIP – CK consideration for content (max 2/3 words)
Sometimes a single status is enough. For example if you need to tell users which parts of an application they’ve finished and which they have not, you may only need a ‘Completed’ status. Because the user understands that if something does not have a status, that means it’s incomplete.
Statuses should be helpful to users. The more you add, the harder it is for users to remember them. Start with the smallest number of statuses you think might work, then add more if your user research shows there’s a need for them.
Use colour to help distinguish between different statuses – or to help draw the user’s attention to a status if it’s especially important. For example, it probably makes sense to use red a status that reads ‘Urgent’.
Do not use colour alone to convey information because it’s not accessible. If you use the same status in more than one place, make sure you keep the colour consistent.
Because status with solid colours tend to stand out more, it’s usually best to avoid mixing solid colours and tints: use one or the other. This matters less if you’re only using two colours.
The below criteria all need to be met for a component to be considered as fully developed for use within the ASP Digital Design System.
| Development criteria | Status |
|---|---|
| WCAG 2.2 compliant | Not started |
| WCAG 2.1 compliant | Completed |
| HTML / Nunjucks version | Completed |
| Figma version | Not started |
| M365 versions | Completed |
| Documentation | In progress |
Suggest an edit to this system, or any of the components in it, by submitting a Design System change request.