Any function carried by a mid-air gesture needs a non-gesture equivalent path

What it is

Every function that can be finished by a mid-air gesture must also be finishable by a non-gesture equivalent path: a button, a remote, a keyboard, voice, a switch. Equivalent means the same task outcome, not “somewhere in settings you can change something like it.” This is a function-level reachability requirement, not the emergency script for when recognition is collapsing, and not a cost comparison that decides whether to use gestures at all. Gesture may be the primary path; it must not be the only path.

Why it happens

The mid-air channel leaves service for body, environment, skill, and social setting. If the function hangs only on that channel, leaving service means the function vanishes. A button does not need a skeleton, a remote does not need lighting, a keyboard does not need a stance. The equivalent path unbinds the function from a single sensor. Without it, the product is “touchless” in the brochure and “nobody can move it” in failure. Equivalence also means one application state: if the gesture set volume to 40, the button should continue from 40, not open another, unsynchronized volume. Paths may be asymmetric (gesture fast, button slow); the outcome space must cover.

Studying it

List every command triggered only by gesture, turn the gesture channel off (cover the camera or stop recognition), and see whether the task can be finished. Record unreachable functions, detour length, and whether users believe “this one is wave-only.” Compare “there is a menu, we claim” with “can be found in 30 seconds with eyes on the task.” Recruit people who cannot stably perform mid-air motions, rather than only having intact arms demonstrate the spare button.

Where it stops holding

An art installation may deliberately have no second path, with failure as part of the piece—and should say so on the label. A safety stop sometimes must be dedicated hardware, and mid-air should not be primary. Voice that cannot state the parameters, or that dies in site noise, does not count as a non-gesture path already provided. In a headset, “equivalent” may be a controller or gaze-plus-click, and it still has to work when both arms cannot be raised.

Applying it

• Make a function table: one gesture command per row, a non-gesture method in the next column. Empty cells do not ship.
• Write both paths into the same state so there are not two volumes or two playback heads.
• At acceptance, physically block the camera and walk core tasks. A step that cannot be walked is a missing equivalent; do not teach a new gesture on the spot to patch it.

Related

• Same group: C4.28.2 The non-gesture path serves recognition failure, fatigue, and bodily difference among other failure modes · C4.28.3 The non-gesture path cannot be buried deeper than the gesture path, or it exists only in name · C4.28.4 The cost of providing the non-gesture path should be counted in the overall cost of the gesture design
• Adjacent: C4.01 Definition and fit of mid-air gestures · C4.25 Predefined fallback paths
• Search: equivalent path · alternative input · not gesture-only