Typing the name breaks click-through

What it is

Typed confirmation asks someone to generate text rather than click once more. Generation uses a different motor channel, pulls “OK” out of the aiming skill, and breaks the automated click chain. This entry is only about why typing interrupts click-through. It is not about what the typed string must be, and not about how expensive the method is.

Why it happens

Click-to-confirm reuses a compiled pointing act: same place, same gesture, same rhythm. Typing has to retrieve the object name, organize keystrokes, and check the string on screen, so working memory is forced to load identity. Macros and repeated-click scripts usually do not type, so the channel also blocks non-human pass-through. The break is the channel switch, not another modal. If a clickable “OK” still sits under the field and need not match first, the switch never happened.

Studying it

Compare, on an irreversible delete: an ordinary confirm, typing any characters, and typing a specified word. Include a repeated-click script as a non-human actor.

Independent variables: whether the second channel is typing, whether a match is required, whether a script can complete the act. Dependent variables: human click-through rate, script success, whether gaze meets the object name before typing, time to complete.

Lab participants know they will type and become unusually careful. Closer to life: insert typed confirmation after a long run of ordinary confirms, and see whether automation stops at the channel switch.

Where it stops holding

Password managers and autofill may dump the name in, bypassing the switch; detect non-human paste or require typing from a source that cannot be filled. For people with motor disabilities, typing costs far more than clicking; an authorized alternative channel is required, rather than making the highest friction the only door. On mobile, the keyboard can cover the consequence copy, so the interruption happens and the check does not. If “handwrite the name” on a touchscreen is recognized as a tap, the channel did not change.

Applying it

• For the highest-stakes irreversible acts, bind the primary button to a successful typed match; keep it inert until then.
• Do not place an “OK” beside the field that can be clicked without a match; that rolls typed confirmation back into an ordinary confirm.
• Offer assistive technology and authorized delegates an equivalent, still-explicit consent path, rather than forcing typing.
• Verify with a repeated-click tool: the path must not complete. On a human recording, watch whether the click chain breaks at typing. If the chain does not break, the channel did not change.

Related

• Within the group: H3.07.2 What they type must name the thing being destroyed · H3.07.3 Typed confirm is expensive; keep it rare
• Adjacent: H3.06 Friction for destructive actions · H3.05 Confirmation dialog abuse · E6.05 Confirmation dialogs
• Search terms: typed confirmation · click-through · channel switching