Choose against the task constraints
The example enquiry asks for one service mode: onsite, remote or not yet decided. Each has a short explanation. The requester must choose one but may legitimately be unsure. A second field contains thirty existing branch codes and has a different scanning need. These numbers are example constraints, not universal UI thresholds.
| Condition | Visible radio group | Select menu |
|---|---|---|
| Compare explanations | Labels and notes stay visible | Collapsed menu hides unchosen alternatives |
| Constrained vertical space | Needs room for all options | Uses less closed-state space |
| No decision yet is valid | Include an explicit unsure option | Use a real unsure value rather than an empty sentinel |
Use visible radios for the three explained service modes. The branch-code field can use a different control after testing lookup needs. Avoid preselecting a service merely to satisfy validation when the requester has made no choice.
An unsure answer differs from no answer
| Input | Meaning | Validation result |
|---|---|---|
| remote | Requester chose remote | Complete choice |
| unsure | Requester chose not yet decided | Complete choice |
| empty | No option selected | Ask for a choice |
Does an unsure value need the same error as an empty value?
Show the worked answer
No. Unsure is one of the valid answers in this example. Empty has no choice. Store distinct values so staff can route a request for advice.
Check the chosen interaction
- The group has a meaningful accessible name.
- A saved unsure value survives reload and language switching.
- No initial value falsely records a user decision.