Choose against the task constraints
An invented dispatch board distinguishes ready, held and sent. Staff must act on the first two differently. A red mark alone does not tell them whether a record failed validation, awaits a decision or is cancelled. The worksheet defines these local states, not a universal colour convention.
| Condition | Colour-only indicator | Labelled state with optional colour |
|---|---|---|
| Understand the next action | Colour needs a separate interpretation | A state label can name the actual condition |
| No colour distinction available | Meaning may disappear | Text remains available |
| Several held reasons | One colour merges different decisions | State and reason can stay separate |
Use state text as the primary operational signal and colour as an additional cue. Show a reason only when it changes the staff action. Do not turn ready, approved and sent into one success-coloured state.
State text determines the next task
| Record | State / reason | Next action |
|---|---|---|
| D-1 | Ready | Dispatch according to approved process |
| D-2 | Held; destination missing | Verify destination before dispatch |
| D-3 | Sent; reference SH-3 | Track existing shipment |
Should D-2 and D-3 share one actionable state because both have coloured badges?
Show the worked answer
No. D-2 needs destination verification, while D-3 already has a shipment reference. Their state and next action remain different regardless of colour.
Check the chosen interaction
- Removing colour leaves every state understandable.
- Screen-reader text names the same state as the visual label.
- State changes do not silently imply a completed operation.