High-contrast color is a scarce budget that should be spent only on states needing action now

What it is

High-contrast, high-saturation color is a scarce visual resource that should be allocated, like a budget, only to states that genuinely require immediate operator attention and action — a strategy usually called a salience budget or colour coding budget. If navigation chrome, branding, and normally operating equipment icons are rendered just as vividly as an alarm state, the anomaly loses the relative colour advantage it is supposed to have. The anomaly has not become less vivid; everything else has been raised to compete with it.

Why it happens

Salience is a competitive relationship, not a fixed property of any single object: a red icon stands out sharply against an all-grey display, but add five more equally red icons and they cancel each other's salience — attention gets spread thin and priority flattens to "everything looks equally important." Narrowing high-contrast color to states that actually require action does more than preserve salience: it builds a learned association in the operator. Seeing intense color rarely means it comes to reliably signal "this needs something from me," which shortens the step from noticing to acting because the operator no longer has to first judge whether the color really matters. Once strong color is spent on decoration or on information that needs no response, that learned association breaks down and operators are back to checking the meaning of each color individually.

Where it stops holding

High contrast should not be equated with the highest severity level; how much visual resource a state deserves also depends on its allowed response time and who owns handling it — a state with a short response window can warrant strong salience even if its consequence is not the worst case. Sustained exposure to the same high-contrast signal also produces habituation, so its pull on attention fades over time, which makes high contrast a poor choice for a state that needs to stay pending for a long stretch without being resolved. Color cannot carry the whole coding load alone either: operators with color-vision deficiencies, monochrome printouts, and degraded display modes lose or distort color information, so sound cues, shape differences, and fixed position still need to be kept as redundant channels.

Applying it

Inventory every element on screen currently using saturated, high-contrast color; anything that does not carry the meaning "the operator needs to do something" — brand colors, decorative icons, color blocks used only to distinguish areas — should move to low chroma or drop the color distinction entirely. For what remains as genuine state color, grade it by consequence severity and allowed response time, and fix one hue per grade, avoiding the inversion where a more important state ends up with weaker visual intensity because it is used less often. For a persistent anomaly the operator has already acknowledged, the stimulus intensity can be reduced after the first capture of attention — for example switching from blinking to steady — but some other cue must keep signalling that the state is still unresolved, rather than letting it fade out entirely as the stimulus drops. Validate with scenarios that mix several priority levels at once, measuring the time to the operator's first fixation on the highest-priority object and whether their first action targets the correct one.

Related

• Same group: Y3.12.1 Low-saturation background for anomaly salience · Y3.12.3 Salience saturation · Y3.12.4 Decorative depth cues in control displays
• Nearby: Y3.03 Color and coding conventions · Y2.03 Alarm priority classification
• Search terms: salience budget · colour coding budget · high-performance HMI · alarm priority