Step by Step

Color-blind accessibility: how to make a status dot readable

7 min read
Mikhail ShaymardanovWeb Quality and Accessibility Expert

A Status column colored like a traffic light brings together three colors that red-green color blindness, the most common type, confuses. About 1 in 12 men has trouble telling certain colors apart, according to the US National Eye Institute. The fix is a word written next to each dot or, when space runs out, a shape unique to each status. Chrome’s built-in color blindness simulator shows the result.

A word for every status


#What a color-blind person sees in a color-coded Status column?

When only color separates the dots in a Status column, a color-blind person has trouble telling some statuses apart. The most common type of color blindness makes red and green hard to distinguish.

A rule exists for exactly this situation: use of color, success criterion 1.4.1 of the Web Content Accessibility Guidelines (WCAG). It is aimed first at sighted people, who may not use any assistive technology such as a screen reader. The W3C, which publishes WCAG, also names people with partial sight, some older users and anyone on a monochrome display.

In the European Union, online shopping comes under Directive (EU) 2019/882, the European Accessibility Act. Since June 28, 2025, it has applied to every shop that sells online to consumers, microenterprises (the smallest firms) aside. EN 301 549, the European standard written as one voluntary way to comply with the Act, requires every web page to meet this criterion.

An accessible status cell comes down to three rules:

  • The status reads without its color, through a word or a shape.
  • It shows at rest, without hovering or clicking.
  • A screen reader gets the same status the screen shows.

On the “My orders” page of The Dice Attic, an online board game shop, five orders show five statuses. Each status is a 12 px dot with no text, named only by an aria-label, a label hidden in the code for assistive technology. A color key above the table explains the colors.

Screenshot: the “My orders” page of a board game shop, with a key of five colors above a table of five orders whose Status column shows only one colored dot per row.Marker 1. The five dots in the Status column, with no words. Marker 2. The key of the five colors, above the table.
In “My orders”, each status is just a 12 px dotmarker 1; only the color keymarker 2 says that green means “Delivered”.

#How a color-blind person sees green, orange and red?

Deuteranopia is a complete type of red-green color blindness: the eye can’t tell red from green at all. Chrome simulates it, and its documentation describes a confusion of greens, reds and yellows.

With that simulation on, we picked each dot’s color with an eyedropper. Green, orange and red turn into three brownish yellows, the green and the red almost identical, while the blue of “Shipped” stays blue. Britain’s workplace safety regulator, the Health and Safety Executive, lists traffic signals among the typical difficulties of red-green color blindness.

Chrome shows a complete type here, an extreme case: the most common red-green type is mild. As for conformance, no simulation proves it.

Screenshot: the same page under Chrome’s deuteranopia emulation; in the key and in the table, the green, orange and red dots have turned brownish yellow, and the blue one is still blue.Marker 1. The dots for Delivered, Processing and Canceled, now brownish yellow.
With deuteranopia, the dots for “Delivered”, “Processing” and “Canceled”marker 1 turn into three brownish yellows; the one for “Shipped” stays blue.

#What the column looks like when no color gets through?

Chrome’s “Achromatopsia (no color)” option replaces every color with a gray. This time, the red of “Canceled” and the gray of “Awaiting payment” give exactly the same gray, #727272, and the blue of “Shipped” is almost impossible to tell from it. A canceled order then looks just like one awaiting payment.

The contrast ratio predicted this match. It compares only lightness, and in full color this red and this gray already score 1.00:1, the lowest possible score.

Screenshot: the same page with no color at all; every dot is gray, and the dots of the first two orders are exactly the same gray.Marker 1. The dots for Canceled and Awaiting payment, in the same gray.
With no color at all, “Canceled” and “Awaiting payment”marker 1 take exactly the same gray.
Green, orange and red turn brownish yellow with deuteranopia; with no color, red and gray give the same gray
Status and original colorWith deuteranopiaWith no color
Delivered
#16a34a
#958951#8e8e8e
Shipped
#2563eb
#0064e8#6d6d6d
Processing
#f97316
#baa60c#9a9a9a
Canceled
#dc2626
#8f801b#727272
Awaiting payment
#6b7280
#6c7180#727272

#What to add so a status dot doesn’t rely on color alone?

Each status needs a cue that shows in the cell without hovering: ideally its word, or else a shape of its own.

The column has to look different: people who confuse colors don’t necessarily use assistive technology, so the W3C asks for a visible alternative to color. The color can stay, backed up by that cue.

#Is an aria-label, a tooltip or a color key enough?

None of the three is enough: each one lacks a visible cue in the cell, at rest.

An aria-label appears nowhere on screen, and not every screen reader reads it.

In many browsers, the tooltip of the title attribute only appears on mouse hover, so keyboard and touchscreen users never see it. The HTML standard advises against relying on it for that reason.

That leaves the color key. With deuteranopia, its dots for “Delivered” and “Canceled” look almost the same, so it can no longer say which is which. In the W3C’s own example of a color key, the number beside each color in the image is what makes it readable.

#How to write the status next to the dot?

We recommend the visible word, written in the cell. The dot then becomes decoration, hidden from screen readers with aria-hidden="true". Everyone reads the word, whether they use a mouse, a keyboard or a touchscreen. Its only drawback is width: on our demo, “Awaiting payment” alone sets the width of the column.

Avoid

Screenshot: the row for order #20431 from November 9, 2026, whose Status cell holds only a green dot.Marker 1. The green dot, alone in the cell.
<td><span class="dot delivered" aria-label="Delivered"></span></td>

Correct

Screenshot: the same row, with the green dot followed by the word “Delivered”.Marker 1. The green dot followed by the word Delivered.
<td><span class="dot delivered" aria-hidden="true"></span>Delivered</td>
On its own, the green dotmarker 1 only says “Delivered” to people who can see green; written next to it, the wordmarker 1 reads the same with deuteranopia or with no color at all.

When a team’s design system, its shared library of interface components, calls for the dot alone, the UK government’s design system offers a counterargument. Each of its status tags shows a word, with color only as backup. An icon for each status, such as a check mark, a clock or a cross, also helps people tell states apart, as Apple recommends; as decoration, the icon gets aria-hidden="true".

#What to do when the word doesn’t fit the column?

When the column is too narrow, each status gets its own symbol, drawn in white inside its dot: a check mark, an arrow, a clock, a cross, three dots. This option comes with two requirements.

The first is a name for screen readers: the dot becomes an information-carrying image, with role="img" and an aria-label that gives the status.

<span class="dot processing" role="img" aria-label="Processing"></span>

The second is a 3:1 contrast between the symbol and its dot, which WCAG requires for any part of a graphic needed to understand it. On the demo, the white clock on orange only reaches 2.80:1, and the check mark on green barely passes at 3.30:1. A thin stroke also looks paler once the browser smooths its edges, so it pays to aim above the minimum.

Screenshot: a narrow view of “My orders”, each status reduced to a colored dot carrying a white symbol: three dots, a cross, a clock, a check mark and an arrow.Marker 1. The orange Processing dot, with its white clock.
In the narrow column, the white clock on the orange dotmarker 1 only reaches 2.80:1, below the required 3:1.

For the clock, a darker orange solves it: on #c2410c, the white symbol climbs to 5.18:1. Measure each of your symbols against its dot with our contrast checker before you settle on a shade.

The shape alone, chosen to save space, turns out to be the most demanding option. Next to the written word, the dot is mere decoration. WCAG no longer requires its contrast, and the orange at 2.80:1 can stay as it is next to “Processing”.

Non-text contrast (WCAG 1.4.11): how to check a border, focus indicator or icon when DevTools shows no ratio

#How to test your site with Chrome’s color blind simulator?

Chrome already includes a color blindness simulator: the Emulate vision deficiencies list, in the Rendering tab of its developer tools.

  1. On the page you want to test, open the developer tools.
  2. Press Cmd+Shift+P on a Mac or Ctrl+Shift+P on Windows, type “Show Rendering”, then press Enter: the Rendering tab opens.
  3. Under Emulate vision deficiencies, choose “Deuteranopia (no green)”, then “Achromatopsia (no color)”.
  4. Switch back to “No emulation” when you’re done.

Chrome has no grayscale option: Achromatopsia stands in for it. Firefox simulates these deficiencies too, in its Accessibility Inspector.

On The Dice Attic’s corrected page, we ran both tests again. With deuteranopia, green, orange and red still turn brownish yellow; with achromatopsia, red and gray still give the same gray. This time, though, every row reads in plain words, “Delivered”, “Processing”, “Canceled”, and those look-alikes no longer matter.

Screenshot: Chrome with its developer tools docked at the bottom; at the top, the orders table with a word next to each dot; at the bottom, the Rendering tab and its Emulate vision deficiencies list.Marker 1. The Emulate vision deficiencies list, set to Deuteranopia (no green). Marker 2. The Status column, each dot followed by its word.
With “Deuteranopia (no green)”marker 1, three dots stay brownish yellow, and each statusmarker 2 reads in plain words.
How to check the contrast ratio of text in Chrome DevTools

On a live site, Includdy flags empty dots named by an aria-label. Its guided fix puts the faulty HTML side by side with a corrected component, to review before you integrate it. For a column of symbols, the contrast checker measures each one.


Share this article

Frequently asked questions

No: a status needs another visual cue. The W3C counts a lightness difference of at least 3:1 as an extra cue for telling two elements apart. When people have to recognize a specific color, though, such as a green outline for valid and a red one for invalid, the W3C requires another visual cue whatever the contrast.

None of the five status colors in our demo reaches 3:1 against another anyway: the highest pair, blue against orange, tops out at 1.84:1.

Yes, though far less often than men, according to the US National Eye Institute. To inherit red-green color blindness, a woman needs the gene on both of her X chromosomes, which rarely happens.

Britain’s workplace safety regulator, the Health and Safety Executive, puts inherited red-green color blindness at 0.4% of women, against 8% of men.

Very rarely. Seeing no color at all, called achromatopsia, is rare: the most common type of color blindness makes red and green hard to tell apart, and another type makes blue and yellow look the same.

The “Achromatopsia (no color)” option in Chrome’s simulator is still useful: it shows what is left of a page when no color gets through, on a monochrome screen for example.