Imagine a US service company tracking AI-written customer replies with red, yellow, and green dots. A manager asks which replies need human review, but a colleague sees a row of similar circles. The problem is not the model. It is how work is represented. This fictional board explores a small change: give each state a name, a shape, and a next step.

W3C explains that color should not be the only way to convey information.[1] We suggest replacing an amber dot with “Needs review,” then adding “Check the amount before sending.” Avoid instructions such as “Handle yellow items first.” Do not let green mean every kind of completion. A model finishing its draft, a person approving it, and a customer receiving it are three different facts.

A pause symbol can accompany “Waiting for information,” while a warning triangle accompanies “Check required.” In our example, text explains the business state, shapes support scanning, and color provides an extra cue. Use the same names in lists, detail views, and exported reports. Avoid calling something complete on one screen while leaving only an unexplained green dot elsewhere.

W3C has a separate non-text contrast requirement for graphics needed to understand content and relevant visual information about controls, with exceptions.[2] Adding text does not resolve every contrast issue. Making red and green darker does not explain the business meaning. Ask separately: can people perceive it, and can they understand it? This article is not a complete accessibility audit or a legal determination.

We suggest giving a fictional queue to a colleague who did not design it. Ask them to find review items, explain the blocking reason, and identify the next step. Repeat with a grayscale version as an initial check and note remaining color dependencies. Grayscale does not simulate every visual impairment or replace full testing. Fix labels that could misdirect a handoff, so an ambiguous board does not undermine faster AI drafting.