Lozenge, Badges & Chips

Showcase short metadata in a compact format.

UsageOverview

Labels and badges both represent an important state of an entity: unread notifications, task statuses, approval stages, among others.

Chips allow users to compact entered information such as email addresses, make selections, display filters, or trigger actions.

How to use

Labels

Badges

Chips

How not to use


AnatomyWriting & Tone

Labels** are concise yet clear. Avoid those that are too big and make it difficult to glance over.

Badges** call out unattended events in the context of an activity. It is adequate to include a number, a single symbol, or nothing at all, given that the shape and color already fulfill its main function; whatever figure is added should help complement the nature of the callout.

Chips** present options or condense information like email addresses.


BehaviorTooltip rules

Always try to make labels, badges and chips clear. If a label isn't clear enough, a tooltip might be added to clarify the meaning of that label.


VariationsLabel

Badge

Chip

Color

Refer to the appropriate section on Color System.

States

Use a dismissable label if it is susceptible to be removed — perhaps from a list. The whole label should be the click target.

Chips


Overflow

If a label or a chip is over 20 characters long, it is advised to truncate it with an ellipsis and provide a tooltip with the full label name.


Best practices Accessibility

The use of color only provides a visual indication that is not conveyed by screen readers. Information denoted by color should either be obvious from the context or included through the use of a hidden text class like.sr-only .

The accessible text that will be read by screen readers in a label should always include context. User "3 notifications" instead of just "3".


Feedback

We would like to get your feedback. Tell us how you use this component in your projects and how we can improve it.

StyleLabels, Tags

Badges

Chips