Skip to content

Button

Buttons trigger actions. Use them to submit forms, navigate, or initiate workflows.

Variants

Each variant has a specific function. Use them consistently so users learn what each means.

VariantPurpose
PrimaryPrincipal call to action on the page. Only one per screen (header and modal excluded).
SecondarySecondary action paired with a primary — e.g. "Cancel" or "Back". Never use in isolation.
TertiaryLess prominent action. Works on its own or alongside a primary when several actions compete.
DestructiveActions with destructive consequences — delete, remove, revoke. Reserve for irreversible intent.

Design tokens

TokenValueDescription
background/action/primary
#318272
Primary background
background/action/primary/hover
#226558
Primary hover
background/action/primary/active
#15483e
Primary active
text/inverse
#ffffff
Primary label
background/surface
#ffffff
Secondary background
border/default
#cccccc
Secondary border
background/action/destructive
#bc1700
Destructive background
radius/sm
4px
Button corner radius

Guidelines

Do
  • Use 1–3 words that describe the action: "Save changes", "Create account"
  • Use sentence case, not ALL CAPS
  • Use one primary button per screen section
  • Pair icon-only buttons with aria-label
  • Explain why a button is disabled via tooltip or helper text
Don't
  • Use vague labels: "OK", "Yes", "Click here"
  • Place two primary buttons side by side
  • Use a button for page navigation — use a link
  • Use a destructive button for minor, reversible actions
  • Skip the label on icon-only buttons without aria-label