Radios mean exclusive and exactly one
Aliases: radio button · mutually exclusive choice · required single select
What it is
A radio button packs a set into a single truth value: options exclude one another, and the set must have a value at submit. It constrains two things at once — no stacking, no blank — rather than being “a checkbox drawn as a dot.” Delivery method, a statutory gender field, one payment rail are this kind of set. If the domain allows “none” or “several,” radio semantics already fail; change the control rather than the hint.
Exclusive-and-required names the data model, not a pre-ticked opening. An untouched group may render empty until the first click; empty is undecided, not a legal answer.
Why it happens
A circle with a solid fill has been trained as the unique occupant of a slot. Picking one ejects the previous one because people read the group as a position, not a row of independent propositions. Required follows from the same reading: a position is supposed to hold a value, and empty means the question is unfinished.
Squares used for mutex, or dots used for additive items, let shape override copy. People act on shape: they refuse to stack when they should, and they feel forced to pick when they should leave blank. The group also needs a visible boundary — two adjacent clusters of dots with tight spacing get read as one mutex, producing cross-group theft or a refusal to switch inside the real group.
Studying it
Give the same question two cardinality rules: exactly one, or several allowed. Cross that with glyph so materials are shape-consistent or shape-conflicting.
Independent variables: exclusivity, whether exactly one is required, circle versus square, group spacing. Dependent variables: stacking attempts, blank submits, cross-group errors, whether people can say “how many may I pick.”
Asking “can I pick another?” after submit is stabler than think-aloud mid-task: action follows habit; the correct term often appears only afterwards.
Where it stops holding
A segmented control is also exclusive, but it switches a view, not a form field; drawing radios as segments makes people expect the whole page to change. A switch is one binary, not “two radios”; if yes/no still needs a third “undecided,” radios beat a switch. With many options the mutex still holds, but scan cost pushes the display into a menu — a presentation issue, not a cancelled exclusion. Read-only echoes should become plain text; a dead dot that still looks like “must pick one” invites clicks that cannot land.
Applying it
- Use radios when the model holds exactly one; stacked choice becomes checkboxes, an immediate binary becomes a switch.
- Mark the mutex with a group label and spacing so two clusters are not read as one.
- Undecided may look empty; a missing value at submit must block on this group, not let the system quietly pick.
- How to check: ask someone new “can I pick two?” and “can I submit none?” Both answers must match the model.