C7.05.3Non-voice fallback in noisedesignresearch

Noisy settings require a non-voice path

Aliases: fallback input · noise degradation · multimodal fallback

What it is

Noise can take the voice channel below usability while the task remains: navigate, reply, silence an alarm. Noisy settings therefore need a completion path that does not go through recognition—touch, keys, a wheel button, a keyboard. The requirement is task continuity when the channel fails, not another turn of the denoiser.

Why it happens

Voice is most valuable when hands or eyes are busy, and those scenes are often loud: cabins, kitchens, shop floors. Once the SNR door is crossed, keeping voice as the only entry locks the task. The non-voice path has to be reachable at the moment of failure, not buried in settings afterwards. Visual or tactile confirmation must also be possible in gloves or while watching the road, or “we have a fallback” exists only on an architecture slide. Denoising and beamforming can raise the door; they cannot guarantee it will never be crossed, so the fallback is not optional decoration.

Studying it

Run real tasks under unusable SNR or overlap, comparing voice-only, voice plus touch, and voice plus a physical key on completion rate and safety-related behaviour (glances to the screen, hands off the wheel). Record how many steps it takes to find the fallback after voice fails. If the experimenter hands over a keyboard after failure, discovery cost is understated.

Where it stops holding

People who are deaf or hard of hearing need a non-voice path for reasons other than noise, and the same fallback often serves them. Close-talking earphones can remain usable in noise; forcing a switch to touch then gets in the way. The fallback should appear after detected failure, not disable voice the instant a noise sensor lights. Legal or safety rules (driving) may forbid voice for some actions; that constraint stacks with SNR failure. A screenless speaker’s non-voice path may be a companion app on a phone, which is harder to discover and even less dispensable.

Applying it

  • Place a one-step touch or key equivalent beside the voice path, especially for cancel, stop, and emergency-related actions.
  • After repeated recognition failure or estimated SNR too low, prompt the fallback; do not only repeat “please say that again.”
  • Walk full tasks in the target noise: from failure to finishing on the fallback, step count and eyes-off-road time must be acceptable.

Related

  • Same group: C7.05.1 Signal-to-noise ratio directly determines whether recognition is usable · C7.05.2 Attribution when several people speak at once
  • Adjacent: C7.06 Hands-Free and Eyes-Free Use · C7.17 Switching Between Voice and Keyboard
  • Search: fallback input · voice in noise · multimodal redundancy

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/C7.05.3