A touch fallback path must remain available
Aliases: touch fallback · dual-path kiosk · contact alternative · physical button backup
What it is
After a public terminal moves to hover, QR, or voice so fewer people touch the glass, removing the touch layer or the hardware keys locks out anyone the sensor misses, anyone who cannot perform, and anyone who will not mime in public. Retain a touch fallback path means touchless may be the primary path but must not be the only path: the same task still has to be completable with a finger, a stylus, or a physical button. This is a claim about hygiene-driven public terminals, not a general rule that every gesture needs an equivalent. The missing path here is specifically contact, because contact remains the most stable, least theatrical input on a public screen.
Why it happens
Touchless fails in batches outdoors and in crowds: sun saturates a depth camera, sleeves occlude a skeleton, height misses the capture cone, gloves or carried bags distort hover, side-by-side users scramble attribution. Once failure happens in front of an audience, people rarely retry a different mid-air pose; they leave. A contact path turns “the system does not work” into “I will tap it.” People with strong hygiene concern take touchless; people in a hurry or with weak concern take touch. Both paths have to exist, or one failure mode is written as everyone's failure. A fallback buried in “advanced” or gated behind a mid-air tutorial is not a fallback.
Studying it
Offer touchless and touch together on a live site. Log completion by path, switches after failure, and which path is chosen under disability, gloves, or bright light. Do not retire touch on the strength of a lab recognition rate.
Independent variables: visibility of touch targets, presence of a physical key, whether touch is immediately available after touchless failure, ambient light and gloves. Dependent variables: path split, share who move to touch after touchless failure, task completion, leave rate.
Reading “touchless completion is high” as “touch can go” is a common error—the high rate often comes from the people who already can, and the others have left the denominator. Wheelchair height, children's reach, and one-handed luggage users belong in the sample, not only standing adults in the sweet spot of the cone.
Where it stops holding
Isolation rooms that forbid bare-hand contact may fall back to a foot switch, a membrane key, or a phone, not the same capacitive glass. High-vandalism sites lose exposed buttons to operations, which is not the same as interaction being allowed to have no contact channel. A sealed showcase with no task has nothing to complete. A phone QR code can serve as the contact fallback if the code is readable in one step and does not require an app install; otherwise the failure has only moved to another screen. A fully sealed cabinet with the capacitive layer already removed needs physical keys or a remote session—it cannot be promised as a later add-on.
Applying it
- Let hover or QR be primary, but keep a reachable set of touch targets or hardware keys in the same view that finish the same critical task; do not reveal them only after touchless fails.
- Size and place touch targets for fingers, including seated users, children, and one-handed carrying, not only the depth camera's preferred stance.
- After two consecutive touchless failures, push the touch entry into a more conspicuous position instead of replaying the mid-air tutorial.
- Verify by running the task in bright sun, with gloves, and from wheelchair height; if shutting off either path alone drops completion below an acceptable floor, the other path cannot yet carry the site.