Maturity
Overview
Badges provide supplemental information about the status or importance of a parent element. They aren’t interactive, so they don’t have any associated interaction states. But their parent element can be.
Shape Badges allow us to do it in places where the space is compromised, like in Figures.
Related components
How to use
Sentiment
Semantic colors are intended to draw attention to essential experience elements and, through specific sentiments, assign them a particular meaning that facilitates their differentiation.
More details
- Signify an interactive element.
- Something is active and working as intended
- "This is what you can do"
- "Everything is on track"
- "Live"
- "We want to let you know that this is unavailable."
- "Disabled"
- "Pro" (only available in the Pro plan)
- Something’s not working and requires immediate action because of its importance and severity; regardless if it’s a person’s error or a system error.
- A problem happened, or a person made a mistake that prevented them from finishing their task or a process.
- Indicate actions that are destructive and can’t be undone—they require confirmation.
- "We’ve got a problem, and we need to act now."
- "We’re letting you know about a potential problem."
- "Unverified"
- "This is done; everything went well."
- "Enabled"
- "We’re letting you know about…"
- "New"
- "Beta"
- "AI"
Size
Shape Badges come in three sizes:
- Small (SM – 6px) for Dense layouts.
- Medium (MD – 8px) as the default size.
- Large (LG – 12px) when it complements bigger component, such as the LG Figure.
Crop Border
Crop Border prevents the Badge from blending with its parent element. It's False by default.
Quality checklist
This component passes the following requirements described in our Component lifecycle.
Maturity
α · Design tokens
It uses Ariane design tokens.
α · Official assets
It uses the official Ariane assets (e.g., icons and illustrations) in one of the official sizes.
α · Accessible use of color
Its color contrast ratio is at least 4.5:1 for text and interactive areas.
α · Target areas
Its interactive target areas are large enough for users to accurately select them, following the Fitts law.
α · Naming agreement
Its name is agreed upon and shared between design and development.
α · Responsive L1
Is responsive to different viewport sizes.
α · User-triggered states
If the component is interactive, all its possible user-triggered interactive states are defined.
β · Responsive L2
The responsive behavior has been reviewed and validated by the team.
β · State properties
All the possible state attributes are defined.
β · Docs L1
It has essential documentation with at least primary usage.
β · Use cases
All the uses are audited and refined.
RC · Definition agreement
Its naming and properties are audited and aligned in design and code.
RC · Accessible L1
Its accessibility is manually audited, and any significant issues are fixed.
RC · Docs L2
The documentation covers the most common use cases and is expected to be iterated during the Release Candidate phase.
RC · Storybook
Includes a Storybook playground of the component.
Stable · Stable API
The component and its API remain stable, with no breaking changes for at least one month.
Stable · Adaptive
Supports adaptive design via preference queries.
Stable · Docs L3
Detailed documentation exists for design, content, accessibility, and implementation, including do’s and dont’s.
Stable · Tooling
Tooling (such as linters, codemods, etc.) exists to help with migrations and prevent further use of alternatives.