Home / Foundations / Data visualisation
Data visualisation
The categorical series palette, its contrast record, and the rules that keep charts accessible.
Categorical series — apply in order
light chip + dark chip; ≥3:1 against surfaces; CVD separation checked (Machado deutan/protan)Graphical-object contrast
3:1 is the WCAG 1.4.11 threshold for graphical objects| Token | on white | on dark card |
|---|---|---|
| --dv-1 | 5.19:1 | 3.49:1 |
| --dv-2 | 3.87:1 | 4.68:1 |
| --dv-3 | 3.42:1 | 5.29:1 |
| --dv-4 | 4.11:1 | 4.41:1 |
| --dv-5 | 5.92:1 | 3.06:1 |
| --dv-6 | 5.78:1 | 3.13:1 |
| --dv-7 | 7.90:1 | 2.29:1 |
| --dv-8 | 7.31:1 | 2.48:1 |
Rules
- Sequence matters: use series 1→8 in order; the set is Okabe–Ito derived, contrast-adjusted, and checked for deuteranopia/protanopia separation (min pairwise distance 14/100 under Machado simulation).
- Never use status colours as series colours — a red line must not read as "error". Status stays in --status-*.
- Do not rely on colour alone: label lines directly, vary dash patterns, or annotate; charts must survive greyscale and colour-blindness.
- Small multiples and sparklines can use a single accent; reserve the categorical sequence for series that share a chart.
- Dark mode: the dark series values are lighter, not inverted (see /foundations/platform).
Research basis: Okabe–Ito colour-universal palette (CVD-safe sequence), IBM Carbon data-viz palettes
(curated categorical sequence, monochromatic ramps for ordered data) and Atlassian's chart tokens; all three stress contrast +
distinction over decoration.
Not yet shipped: sequential / diverging ramps. Ordered data (heatmaps, scales) needs a monochromatic ramp rather than the categorical set. Series 1's hue is the natural base; the next token addition should define 5–7 steps with contrast-checked ends.
Triage Design System v0.13.1-experiment — the central, app-agnostic UI design authority.
Source of truth: /tokens/tokens.json. Showcase chrome only:
site/.