Our brand colour is green and we also use green to mean success — is that a problem or am I overthinking it?
Our design system's primary colour is green. It is on the buttons, the links, the active states, the logo, everything. It is simply what our product looks like.
I realised this week that we also use green for success states — a task completed, a service running, a connection healthy. So the same colour means both "this is our brand" and "this is working".
On one screen we have a green button next to a green status dot and they mean unrelated things. Is this an actual problem, or is context enough to carry it?
@a11y_anneke · 2w ago
The accessibility argument arrives at the same fix by a shorter route: never encode meaning in colour alone, brand collision or not.
Around one in twelve men has some form of colour vision deficiency, and red-green is by far the most common. A green dot and a red dot are, for a meaningful fraction of your users, two dots. Everything else — greyscale printing, bright sunlight on a phone, a cheap monitor, a screen reader — degrades colour-only signals too.
So status needs a second channel regardless. Word, icon shape, position, or all three. Once you have done that for accessibility reasons, the brand collision is already solved as a side effect, which is a nice case of the two concerns pointing the same way.
One practical tip: use different shapes for status, not just different colours. A filled circle for running, a hollow circle for stopped, a triangle for warning. Distinguishable with no colour perception at all.
Reply
Report