Show state with more than color
Use color plus icon, label, shape, position, motion, or texture. Color alone breaks in glare, accessibility modes, and tired-human-at-EPCOT conditions.
UX fundamentals lab
A quick interactive guide to selected, unselected, completed, disabled, loading, and focus states — the stuff that makes an interface feel obvious instead of mysterious.
Good state design answers one question instantly: “What is true right now?”
Use color plus icon, label, shape, position, motion, or texture. Color alone breaks in glare, accessibility modes, and tired-human-at-EPCOT conditions.
Tap → visible response. If the system needs time, show loading. If it worked, celebrate or confirm.
Off is quiet/neutral. On is filled/active. Disabled is faded. Focus has an outline. Users should not need a legend to operate basics.
Prefer “Completed,” “Photo taken,” or “Booboo verified” over ambiguous wording. Avoid negative labels that make people mentally reverse the meaning.
A tiny visual dictionary for common UI states.
Binary controls need clear current state, not just a pretty switch.
Good: position + color + label
Try tabbing to it: the yellow ring shows keyboard focus.
Bad: ambiguous visual language
The control has no readable state, no focus affordance, and relies on unclear styling.
For field-use apps, completed items should feel earned, while incomplete items should still invite action.
Incomplete should feel tappable and inviting, not like failure.
A completed card should have a redundant cue: badge, color, and label.
Completed items can quiet down so the next action is easier to find.
Compare a weak state treatment with a clearer one.
Weak
Problem: active state is only subtle text tone. Button says “Done” but not what is done.
Clear
Better: explicit status text, icon cue, color cue, and action-specific button.
Question: If a completed card turns green, is that enough?