Why toggling a setting is easier than reading it

A settings page shows thirty toggles. A user changes five of them in under a minute. Asked afterwards what each one does, they can describe two. The interface made action cheap and comprehension expensive, and the user chose the cheap one.

What everyone sees

Toggles look like user empowerment — the customer is in control of their preferences. The alternative reading, that a toggle is a binary decision stripped of the context needed to make it, is not how the design is described.

What is actually happening

Norman’s concept of perceived affordance describes how interface elements signal what actions are possible without necessarily conveying what those actions mean. Sunstein showed that simplification of choices can increase participation while decreasing comprehension. Mathur and colleagues documented dark patterns in which interface design prioritises action over understanding, creating decisions that are easy to make and hard to evaluate. A toggle maximises action speed and minimises the information needed to act, which is not the same as minimising the information needed to decide.

Why it stays hidden

The design hides the gap by making it feel unnecessary. The toggle’s binary format implies that the choice is simple, and a simple choice does not require a paragraph of explanation. The user infers simplicity from the interface rather than from the subject matter, and the inference is wrong when the setting has consequences the toggle does not describe.