Low-consequence, reversible actions can accept looser recognition thresholds

What it is

Paging, changing a lamp color, previewing a filter: low-consequence and reversible commands can recognize more loosely. An extra accidental page, flipped back, costs less than a wave the system ignores. Looseness is licensed by the consequence structure, not by the gesture being “casual.” If undo is obscure or lives deep in a menu, a nominally low consequence becomes operationally high, and the license is revoked. Thresholds can be tiered by consequence; the license here comes from reversibility, not from “we decided to bias toward false accepts.”

Why it happens

A miss in mid-air feels powerless: the motion happened, the world did not move, people enlarge or quit. A false accept on a low-consequence command is usually one extra step, and if undo is right there (wave the other way, tap restore), expected cost is lower. A looser threshold moves the operating point toward fewer misses. The license has two premises: undo is actually short, and a false accept cannot roll into high consequence (ten extra pages are fine; setting the picture as wallpaper is not). Treating a command whose undo is buried in settings as low-consequence and loosening it is using nominal consequence as a lie. Looseness also does not mean dropping vocabulary constraints: shapes should still separate; only the cut may sit closer to everyday motion.

Studying it

On the same paging motion, compare a strict and a loose threshold, with immediate reverse-page available. Measure completion time, misses, extra pages, and “willing to keep using it” ratings. Then bury undo in a menu and see whether the loose condition remains welcome. Use “an extra page lands on payment” as a condition that breaks the license. Do not test only expert users who already know how to undo in the lab.

Where it stops holding

A false fire with social cost for bystanders (a large screen suddenly sounding, content turning inappropriate) is not low-consequence for the venue even if the operator can undo. Children may not find undo. “Moved a little” on a continuous control and “one extra page” on a discrete command have different cost structures and cannot share one “low-consequence therefore loose” number. If an accessibility user would have to undo with the same already-failing gesture, the license does not hold.

Applying it

• Only commands whose undo completes in one or two steps enter the loose tier. Draw the undo on the same surface where the error happens.
• The loose tier must still block jumps that roll into a high-consequence page, or switch back to strict before that jump.
• Acceptance: under the loose threshold, an extra page should reverse on the spot. Hide undo and test again; if users stick, the license is revoked and the threshold should tighten.

Related

• Same group: C4.27.1 Recognition difficulty and consequence severity should be designed independently, not treated as naturally bound · C4.27.2 High-consequence actions should not rely on a single one-shot recognition result · C4.27.4 When expanding the gesture vocabulary, re-check whether similar gestures map to different consequence levels
• Adjacent: C4.24 Recognition confidence and bias direction · C3.33 Gesture undoability
• Search: reversible · relaxed threshold · low-consequence