001 Contrast

Nine colors that passed design review and failed a measurement

A palette can look finished and still be unreadable. Nine pairs on our own site measured below the legible threshold, the worst at 1.89 against 4.5.

Our own site’s palette was signed off by eye. Measured, nine pairs of small text fell below the threshold for legible contrast. The worst sat at 1.89 against a required 4.5.

Nobody had been careless. The colors came from a reference design that had been looked at carefully by people who care about this. They were simply never computed.

What the number means

Contrast ratio compares the brightness of text against the brightness behind it, on a scale from 1 to 21. Black on white is 21. Identical colors are 1.

WCAG — the accessibility guideline most regulations point at — asks for 4.5 for normal text and 3 for large text. That is not a design opinion. It is the point below which a meaningful share of people stop being able to read the words, including anyone with reduced contrast sensitivity, which eventually means most people over about sixty.

At 1.89, the text was not hard to read. For a good number of visitors it was not text.

Why the eye is the wrong instrument

A designer checks a palette on a calibrated screen, at full brightness, indoors, with young eyes and no glare, at the size the mockup renders. Your customer reads it on a phone held at arm’s length, outdoors, at forty percent brightness, in a case that has yellowed.

The eye adapts. The measurement does not.

This is why the failures clustered where they did: every single one was small text. At display sizes the same colors are fine, which is exactly what makes them survive review — the headline looks great, so the palette looks great.

What we did about it

We did not change a single declared color. Changing brand values to pass a check is the wrong trade, and it is the one most teams make.

Instead we added new tokens for the roles that failed, derived from the originals and taken up to the required ratio. The eyebrow, the terminal placeholder, the small-print green, the muted accent — each got a variant that passes at the size it is actually used.

Then we made it permanent. A script parses the colors out of the stylesheet and computes the ratio for every declared pair, sixty of them, on every build. It reads the stylesheet rather than a list, so it cannot drift as the design changes. One color is kept in the palette as a brand value but the build fails outright if anybody ever uses it for text.

The check runs in under a second and has never once been argued with, because it is arithmetic.

What to check on your own site

Open your booking page or your intake form. Find the smallest text on it — the field hints, the legal line under the button, the placeholder inside the input. Those are where this fails, and they are also the text that tells somebody what to type.

Put the two colors into any contrast checker. If it comes back under 4.5, that text is decoration for part of your audience.

Two things make this worth an hour rather than a quarter. It is cheap — the fix is a color value, not a redesign. And for healthcare specifically it is not purely a kindness: accessibility obligations attach to federally funded providers, and the booking and intake flows are exactly the paths a complaint names.

Our own write-ups are here if you want to see what this looks like on systems that have been running for years, and you can tell us what you are running — the reply is free and a person writes it.

Recognise any of this in your own system? Describe what breaks and a person replies within one business day. Free, and a person is what’s at the other end.

Write to us  ·  The work  ·  What things cost  ·  All writing