Skip to content
UX Atlas
Plate FND·023 · UI foundationGrid C2 · Rev. 2026-08-14

Semantic Color

Colours assigned a fixed meaning, which only works if the assignment is consistent and never the only signal.

UI foundationCraft conventionFoundational

Definition

Semantic colour maps hues to communicative roles: success, warning, error, information and often a neutral or accent intent. The value comes from consistency, since the meaning is learned across the product.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

On this plate
  1. 1Definition
  2. 2The standard set
  3. 3Making a semantic system work
  4. 4The semantic set, and what each must carry besides colour
  5. 5In practice
  6. 6Local chart
  7. 7Sources
  8. 8Continue from here

Reach for this when

  • Defining a colour system.
  • Designing alerts, validation and status displays.
  • Defining the layer between a raw palette and the components that consume it.

Common mistakes

  • Colour as the only signal.
  • Accent colour that collides with a semantic colour.
  • Hue-based token names.

The standard set

IntentTypical hueUsed for
SuccessGreenCompleted operations, valid input, healthy status.
WarningAmber or orangeSomething needs attention but is not broken.
Error or dangerRedFailures, invalid input, destructive actions.
InformationBlueNeutral notices and explanations.
Accent or primaryBrand hueThe main interactive colour.

Making a semantic system work

  • Define each intent once, with a full ramp: text, border, background surface and icon.
  • Name tokens by intent rather than by hue, so the palette can change without renaming everything.
  • Keep the accent distinct from all four semantic hues, or a primary button will read as a status.
  • Provide a dark mode variant for each intent, since semantic colours rarely invert well.
  • Document exactly which situations use which intent, or teams will diverge.

The semantic set, and what each must carry besides colour

RoleAlso needs
ErrorAn icon, a message, and focus moved to it when it interrupts
WarningA statement of what will happen if it is ignored
SuccessA description of what completed, not only a tick
InformationA reason it is being shown now
DisabledAn explanation of what would enable it
SelectedA non-colour indicator, such as a tick, a border or a label

In practice

  1. i.

    Naming by intent, not by hue

    Design tokens

    A token called color-danger-text survives a rebrand from red to a different hue. A token called color-red-600 does not, and every consumer has to be updated.

  2. ii.

    Naming by intent

    Why the token is not called red

    A token named danger can be re-themed, re-hued for a market where red means something else, and understood by anyone reading the code. One named red-600 can do none of those things.

Local chart

FND·023 · Region II · Grid C2

This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  1. [1]

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applies when you are designing

Applied through

Where this shows up as a concrete interface decision.

Short definition

The one-paragraph version, for when that is all you need.

Related concept

Connected closely enough to change how you apply this.