Back
NoteMar ’222 min read

Say the state in words

The Department of Justice issued web accessibility guidance under the ADA this month. One barrier on its list, information shown only by color, is the one dense professional tools get wrong most, and the fix makes them faster for experts too.

Typeface

On March 18 the Department of Justice published guidance on web accessibility under the Americans with Disabilities Act. It covers state and local governments and businesses open to the public. It doesn’t set a technical standard. It names common barriers, says organizations have flexibility in how they comply, and points to WCAG and Section 508 as helpful guidance.

The barriers it lists are familiar: poor color contrast, information shown only by color, images without alt text, videos without captions, forms without labels and pages that only work with a mouse. WebAIM’s annual scan of a million home pages, published this month, shows how common they still are. Nearly 97% of the pages had detectable WCAG failures, with an average of 50.8 errors each, and low-contrast text was on 83.9% of them.

Most of that list gets attention. One item gets less than it should from people who design professional software: information conveyed only by color.

It’s easy to miss because it feels finished. A green dot means running and a red dot means failed, and the designer who chose the colors reads them instantly. Someone who can’t tell those colors apart reads nothing. Neither can a new hire who hasn’t learned the legend, or anyone glancing at a screen across a desk in bad light.

Dense tools are full of these. Status columns, map markers, chart lines and badges all carry meaning in color because color is cheap on space.

When I worked on Uber Studio, a simulation could hold several riders and drivers, each in a different state at the same moment. Engineers had to read the whole scenario at a glance: who’s waiting, who’s dispatching, what just failed. Every account card said its state in words, with one button for the next step.

That was a decision about speed for experts, and it was also the accessible decision. Saying the state in words is an accessibility fix that also makes a dense tool faster for the experts who use it. Color can still help, as a second signal next to the word. It just can’t be the only one.

The DOJ’s guidance leaves teams to decide how they comply. For product teams, I’d start here: find every place your product shows a state with color alone, and add the word.