Data Display

Status Light

Status lights describe the condition of an entity. They can be used to convey semantic meaning, such as statuses and categories.

In review Rejected Approved

Options

Label

Status lights should always include a label. Color alone is not enough to communicate the status.

Semantic Variants

When status lights have a semantic meaning, they use semantic colors. Use these variants for the following statuses:

  • Informative (Active, in use, live, published)
  • Neutral (e.g., archived, deleted, paused, draft, not started, ended)
  • Positive (e.g., approved, complete, success, new, purchased, licensed)
  • Notice (e.g., needs approval, pending, scheduled, syncing, indexing, processing)
  • Negative (e.g., error, alert, rejected, failed)

Non-Semantic Variants

When status lights are used to color code categories and labels that are commonly found in data visualization, they use label colors. The ideal usage for these is when there are eight or fewer categories or labels being color coded.

Size

Status lights come in three different sizes: small, medium, and large. The small size is the default and most frequently used option. Use the other sizes sparingly; they should be used to create a hierarchy of importance within the page.

Disabled

A status light in a disabled state shows that a status exists, but is not available in that circumstance. This can be used to maintain layout continuity and communicate that a status may become available later.

Implementation

Example Name

Description and implementation notes

<p> code example </p>

Information

Checklist

All interactive states

Includes all interactive states that are applicable (hover, down, focus, keyboard disabled).

All Color Schemes

Works properly across all color schemes (light, dark).

Accessible Contrast for Text

Text has a contrast ratio of at least 4.5:1 for small text and at least 3:1 for large text (WCAG 2.0 1.4.3).

Accessible Contrast for UI Components

Visual information required to identify components and states (except inactive components) has a contrast ratio of at least 3:1 (WCAG 2.1 1.4.11).

Defined Options

Includes relevant options (variant, style, size, orientation, optional iconography, decorations, selection, error state, etc).

Defined Behaviors

Includes guidelines for keyboard focus, layout(wrapping, truncation, overflow) animation, interactions etc.

Usage guidelines

Includes a list of dos and don'ts that highlight best practices and common mistakes.

Writing Guidelines

Includes content standards or usage guidelines for how to write or format in-product content for the component.

Internationalization Guidelines

Works properly across various locales and includes guidelines for bi-directionality (RTL).

Keyboard Interactions

Follows WCAG 2.0 standards for keyboard accessibility guidelines and includes a description of the keyboard interactions.

Design Tokens

All design attributes (color, typography, layout, animation, etc.) are available as design tokens.

UI Kit

Includes a downloadable Figma file that shows multiple options, states, color themes, and platform scales.