The two semantics should not overlap on one page

What it is

A page should not let a switch and a checkbox state the same binary fact, nor let near-synonym copy tell the story twice. Semantic overlap is two widgets competing for one proposition: a slider labelled “enable two-factor” and, under it, a box labelled “require a code at sign-in.” People cannot tell which to throw, whether moving one moves the other, or which is source of truth. Overlap is narrower than mixed clocks: even if both write immediately, competing for the proposition makes people afraid to touch either.

Why it happens

People assume each clickable on a page maps to a unique consequence. Two widgets pointing at one consequence shatter that assumption, and the task becomes “guess the mapping” instead of “change the state.” Three common breaks: the same field drawn twice; a child whose proposition equals the master (“turn off notifications” plus a child “receive notifications”); a master switch and a footer “agree to the above” box that write the same bit on submit.

Overlap also invites a sync illusion. People throw the slider and expect the box to tick itself; when it does not, the gesture looks failed. If the two are truly two-way bound, one side’s animation becomes noise: was that my click or the system grabbing the other widget? Bound or not, two entries still compete to explain the state.

Where it stops holding

A master switch plus detail items is not overlap when the propositions actually nest: the master is “does this class exist,” the children are “which channels inside it.” Copy must say the nesting, and children must disable — not remain ticked-looking — when the master is off. A permission matrix with a row box and a header “select all” is a set operation, not a second proposition. A read-only echo beside an editable switch is not overlap if the echo is not a control; if the echo is still clickable, it is two entries. Translation can create overlap at the language layer when distinct fields collapse into synonyms; source copy that does not overlap is not enough.

Applying it

• List every binary proposition on the page and give each exactly one widget. Merge near-synonym sentences before drawing.
• Show master/child hierarchy with indent and disable; do not let a child keep looking like an independent proposition after the master is off.
• Put select-all in a set-tool slot, not as a peer of the first row.
• How to check: hide the glyphs, leave the sentences, and ask someone to pair “these say the same thing.” Each pair is an overlap to delete or re-nest.

Related

• Within the group: E3.04.1 Use a switch for immediate effect, a checkbox for submit-with-form · E3.04.2 Mixing them causes misjudged timing
• Adjacent: E3.16 Tree Multi-Select and Parent-Child Coupling · E3.12 Tri-State and Indeterminate
• Search terms: semantic overlap · duplicate control · master switch