When does color alone fail to communicate, and what has to back it up?

Color alone fails the moment meaning rests on it, so the rule is simple: any state, link, category, or status signaled by color must be reinforced with a second cue, and that cue is text, shape, icon, or pattern. Color is an enhancer, never the sole carrier of meaning. If a user who cannot distinguish your colors would lose the information, the design has put a message into a channel some people cannot receive, and the fix is to duplicate the message into a channel they can.

The reasoning is population, not preference. A meaningful share of users have some form of color vision deficiency, most commonly red-green, and others read your interface in grayscale on a failing display, in harsh sunlight, or through a low-vision filter. For all of them, hue carries little or no signal. The second cue restores the meaning without taking anything away from sighted color users, which is why redundancy here is pure gain: the icon, label, or shape rides alongside the color rather than replacing it. The redundancy also survives conditions that have nothing to do with vision, since a screenshot pasted into a black-and-white document or a chart printed on a monochrome office printer loses every hue while keeping every label and shape.

The classic failure is the status dot or chart that says “green means healthy, red means down” and stops there. A user with red-green deficiency sees two near-identical dots and cannot tell a passing build from a failing one. Back it up and the same row carries a checkmark beside the green and a warning triangle beside the red, or the words “Online” and “Error,” or a solid fill versus a striped one. A second, quieter failure is the form field that signals an error by turning its border red and nothing else: the user who cannot see the red gets no warning at all and submits again, baffled, so the field needs an inline message and an error icon, not just a hue change. In both, the color becomes a fast visual shortcut for people who can use it while the icon or label does the actual carrying for everyone else.

Note one exception: this rule governs color used to convey information, not color used to decorate. A brand-blue header, an alternating-row background that exists only for visual rhythm, or a hero gradient carries no meaning a user must decode, so it needs no backup. The test is whether removing the color would remove understanding. The exception that trips people is color that is doing both jobs at once: a category tag whose color is also its only label is decorative in feel but informational in fact, so it still owes a second cue, while the same color used purely to make a section pretty does not. A required-field asterisk that is red and an asterisk passes; a required field marked only by turning its border red does not. Apply the rule where color is the message, and leave purely aesthetic color alone.

Audit every place color tells the user something and add a non-color cue beside it. Walk the interface in grayscale, then go to each link, status, category, validation state, and data series and ask whether it still reads with the hue removed. Where it does not, attach text, an icon, a shape, or a pattern so the meaning survives, and keep the color as the enhancement it was always meant to be.