Picture a standard navigation bar. Home. Shop. About. Contact. And then, Coupons, in red. Every other link is blue. No underline difference, no icon, no bold. Just the colour. Does this fail WCAG 1.4.1, use of colour?
The question sounds simple but I’m not so sure.
What the criterion actually says
SC 1.4.1 “Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.”
Four triggers. Colour must be the only means of doing one of those four things. The reflex the Coupons link is distinguished from other links by colour alone, therefore the fourth trigger fires, therefore fail.
But that reading is too fast, it skips the word that does the most work in the entire criterion: only. The question is not whether colour is involved, it’s whether colour is carrying something that nothing else is carrying.
Testing each part
Test 1 - conveying information
The spec’s own examples are revealing: “required fields are red,” “error is shown in red,” “Mary’s sales are in red, Tom’s are in blue.” In every case, colour encodes a transferable category, a field state, an error state, a data series identity. Remove the colour and you lose a meaning the text doesn’t provide.
In our nav, “Coupons” is the information. The word is present. The colour adds nothing to its meaning. A person who is colour blind reads “Coupons” and knows exactly what it is.
Test - Indicating an action
All nav links indicate the same action: click to navigate. The red Coupons link does not indicate a different action, an additional action, or a more urgent action in any encoded sense. The colour does not change the verb per se.
3, Prompting a response
The spec’s example here is form fields highlighted to indicate they’ve been left blank. Colour creates an obligation the user must act on. A marketing-highlighted nav link creates no obligation. A person who is colour blind and doesn’t notice the emphasis experiences no functional consequence.
4, Distinguishing a visual element
This is where you could call fail, but the spec is more precise. The failure technique F73 states its objective as avoiding situations where users “cannot identify links.” The operative word is identify, can they tell it’s a link, can they tell what it does, can they tell where it goes.
A person who is colour blind can identify all of that. “Coupons” is readable, it’s in a nav, it functions as a link. The colour doesn’t really do the identifying work - the text and context do. What the colour does is make sighted users more likely to click it. That is a different thing entirely.
The colour is doing marketing persuasion, not communication. 1.4.1 talks about communication not persuasion.
The meaning-assignment test
The spec’s statement of intent says the criterion exists to protect against colour being used “where each color has a meaning assigned to it.” That phrase is the real test. Not whether colour is present. Not whether it creates visual difference. Whether a meaning has been systematically assigned to that colour.
| Scenario | Meaning assigned? | Verdict |
|---|---|---|
| Red = required field across all forms | Yes — consistent semantic rule | ❌ Fail |
| Red = error state throughout the app | Yes — consistent semantic rule | ❌ Fail |
| Red = Mary’s data, blue = Tom’s (chart) | Yes — part of a legend | ❌ Fail |
| Red = promotional content site-wide | Yes — systemic pattern | ❌ Fail |
| Red Coupons link, one-off, no system | No — one-off aesthetic emphasis | ✅ Pass |
But the marketing aspect?
The nudge not landing is a commercial problem for the business. It is not an accessibility failure for the user. They still see the link, they still know what it does, they still have equal access to the offer.
A person who is colour blind is not disadvantaged in any way the spec protects against. They can find Coupons, click Coupons, and use Coupons. The business is disadvantaged because its conversion “nudge” doesn’t reach everyone, but that is an argument for fixing the design, not evidence of an WCAG violation.
What about navigational context?
The spec itself, in the guidance for F73, acknowledges that “navigational links” can be “visually evident from page design and context” — treating them as a distinct case from inline text links where colour might be the only signal that something is a link at all.
F73’s actual failure examples describe body copy links with no underline, indistinguishable from surrounding text except by colour. That is a genuine fail.
A nav bar full of clearly-styled links, one of which is a different colour, is categorically different. The link’s identity, purpose, and function are all communicated without the colour doing any of that work.
The important caveat
⚠️ When this does fail
If your site uses red systematically to mean “promotional” (sale banners, offer badges, discount labels, all consistently red) then you have assigned a meaning to the colour at a site-wide level. A person who is colour blind and misses that pattern would be losing real categorical information. In that case, the one-off nav link argument collapses and the pattern as a whole fails.
The fix is still a minor
Add bold, italic, or an icon to the Coupons link and the question becomes moot entirely.
/* ❌ Fails — colour only */
nav a.coupons { color: red; }
/* ✅ Passes — bold is a non-colour cue */
nav a.coupons { color: red; font-weight: bold; }
/* ✅ Passes — italic is a non-colour cue */
nav a.coupons { color: red; font-style: italic; }
/* ✅ Passes — G183 route: 3:1 contrast vs surrounding links + focus cue */
nav a.coupons { color: #c00; }
nav a.coupons:hover,
nav a.coupons:focus { text-decoration: underline; }The reason to add it should be design quality and good practice — not a misread of the spec.
Does it matter
The reflex fail on any colour-differentiated link is understandable. It’s conservative, it’s defensible, and it avoids arguments. But it produces findings that don’t reflect the actual risk to users, and it trains teams to distrust accessibility guidance as being detached from reality.
A precise reading of 1.4.1 is not a weakening of accessibility standards, it’s a more honest application of them. The criterion was written to protect users from genuine information loss. Applying it to marketing emphasis that causes no information loss doesn’t protect anyone. It just adds noise to audit reports.
The one-line summary
A red Coupons link in an otherwise blue nav bar, with no surrounding colour system, passes WCAG 1.4.1 — because no meaning has been assigned to the colour, and no information is lost to users who cannot perceive it. Add bold anyway. But don’t call it a fail when it isn’t.