Rarely needed; reserve for elevated neutral status.
primary-soft / accent
Selected or brand-associated metadata.
A compact brand moment that must stand out.
info
Informational context.
Information that needs immediate scanning.
success
A confirmed or completed state.
A completion state that is especially important.
warning
A state that needs review.
A time-sensitive warning that needs attention.
danger
A blocked or failed state.
A high-salience failure or risk that needs action.
242424
Size
Use
md
Default size for standalone status and metadata labels.
sm
Compact size with reduced typography for an embedded Badge inside Button or another compact control.
lg
Larger size for elevated standalone metadata that needs more visual presence.
Anatomy
Slot
Purpose
root
Inline status container with tone and tokenized density.
leading-icon
Optional decorative icon before the visible label.
label
Short text that supplies the status or metadata meaning.
trailing-icon
Optional decorative icon after the visible label.
States
State
Behavior
Default
Badge is static metadata, not an interactive control.
Loading
Spinner replaces the leading icon and exposes aria-busy.
Soft
Default low-emphasis treatment for every tone.
Strong
High-salience treatment for urgent warnings, blocking failures, or critical risk.
Size
md is the default standalone size; sm is for compact embedded metadata and lg adds emphasis.
Comfortable / compact
Density tokens adjust height and padding without changing the API.
Motion
State changes should use shared motion tokens and preserve reduced-motion behavior.
Accessibility
Use concise text that does not rely on color alone.
Avoid using Badge as a button or link.
Use tone for semantic color.
Optional icons are decorative, so text must carry the status meaning.
Use leadingIcon or trailingIcon for visual context; the label remains the accessible status name.
Use sm when the Badge is embedded inside a compact control such as Button.
Use strong emphasis only when a warning, danger, or other status needs elevated attention.
Review the shared responsibility and evidence boundaries in the Accessibility foundation alongside this component-specific contract. Use the Spacing & layout foundation for shared density, wrapping, overflow, reflow, and component-versus-product ownership guidance. The Color foundation, Typography foundation, and Localization foundation define the shared visual-role, text-resilience, direction, and locale boundaries used by component examples.