The box is already checked. Continuing only requires leaving it as it is, and the route seems shorter. Yet a choice preceded that saving of time: someone decided which answer should be present when the page opens.
A default can be useful. It may avoid repeating a frequent preference or offer a starting point. The problem appears when the presence of a value is read as if someone had just chosen it, erasing the difference between accepting, failing to notice and not intervening.
Two beginnings for the same control
The sample contains two groups with the same alternatives, A and B. The first has no preselected answer; the second starts with A. These are not consent requests and no data is sent. Choices remain in the document and the reset command returns each group to its own initial state.
Two initial states
That reset detail matters: returning to the beginning in the second group means selecting A again. The command does not clear every possible choice; it reconstructs a situation defined by the design. Understanding what it does requires knowing that situation.
A present value does not tell us who chose it. Attributing an action to the person would require distinguishing the initial state from later interventions. The example does not record them: it lets us observe the relationship between the two beginnings without deriving behavioural statistics.
The consequence of a change
W3C’s guidance on On Input asks that changing a setting should not cause an unexpected change of context. Choosing A or B in the sample only updates the control; no page opens automatically.

A setting may have wider consequences in a real system. It might change what is shown or the route an operation takes. Those consequences should be understandable without hoping the person opens every detail before proceeding.
The initial value’s appearance deserves attention too. A selected option may be more prominent than an explanation qualifying its meaning. If visual hierarchy encourages moving on, a formally present sentence may remain difficult to encounter.
Keeping the starting point recognisable
The two AI-generated illustrations show a token already placed and a lever held by a counterweight. They are metaphors for the initial state, rather than evidence of measured influence on people. The actual comparison is between the page’s native controls, usable without JavaScript as well.
I draw no rule from this example that every setting must begin empty. There are situations in which an explicit default supports the task. I care that it is not confused with a newly expressed answer, and that changing it has a concrete place in the interface.
Designing a default means taking responsibility for what happens when someone does not intervene. This part of the route exists even in the silence of a control left as it was.
