--- id: status-icon-and-text title: A status message always has its icon and its wording status: decided area: color tokens: [color.status.error.bar, color.status.error.text, color.status.error.tint, color.status.warning.bar, color.status.warning.text, color.status.warning.tint, color.status.success.bar, color.status.success.text, color.status.success.tint, color.status.info.bar, color.status.info.text, color.status.info.tint] applies-to: [prototype, components, design-site] check: manual source: designer decision 20 Nov 2026 (docs/f1/colour.md row 5, docs/f1/colour-decisions.json) --- # A status message always has its icon and its wording Error, warning, success and info are never shown by colour alone. Each carries its own icon and a text that says what is the matter; the colour comes third. The default form is the **tinted** message: dark role text and icon on a pale tint of the role's hue, with a 1px edge in the text colour. The **solid bar** (role colour with the title tone as text) is for the one attention moment a screen may have, not for every message. ## Why The four status hues share one lightness (about L 0.64 for bars, 0.50 for text) so they read as one family and all pass WCAG 2.2 on Papier, white and their tints. At equal lightness, colour vision deficiency removes most of the difference: error and warning bars measure ΔE 8 for deuteranopia even at the best hue pair (error 20°, warning 70°), and info and success measure 3 for tritanopia. Icon and wording carry the meaning (WCAG 2.2 SC 1.4.1); the tinted form keeps the dark text, which differs more than the bars do. ## Do - Icon + text on every status message, inline field errors included. - Tinted form by default; solid bar at most once per screen. - Use the role tokens; never a hand-picked hex. ## Don't - Signal a state with a coloured dot or border only. - Put Antraciet text on a solid bar (2.82:1 on the error bar); the title tone is the text there.