Requiring on-screen confirmation cancels that value
Aliases: visual check · on-screen confirm · broken eyes-free
What it is
After a spoken command leaves, if the user must turn their gaze to a screen to check the transcript, tap a candidate, or dismiss a dialog, eyes-free value is cancelled. Hands may still be free; the eyes are back in a touch loop. The issue is not “whether to give feedback.” It is whether feedback forces a visual confirmation before the action counts.
Why it happens
When recognition is uncertain, products push risk onto the user: glance, then tap send. At a desk that is reasonable; in an eyes-occupied scene, that glance is a primary-task interrupt. Partials, homophones, and low-confidence slots all invite checking. Spoken echo or read-back puts the same duty on the ear, without a head turn. If the interface only flashes a transcript and offers no audible confirm or repair, people are trained to “always look after speaking.” The cancelled value is a strategy outcome, not a microphone limit. A status lamp is different: it can prove “listening” in peripheral vision without becoming a confirmation step that must be read.
Studying it
In a dual task, force or not force on-screen confirmation, and measure eyes-off-road time, confirmation errors (wrong execution from sending without looking), and spontaneous glances. Include low-confidence names so real checking demand appears. Short commands such as “lights on” understate confirmation load because they barely need checking.
Where it stops holding
High-cost actions—transfers, deletes, sending to the wrong contact—may need on-screen or dual auditory confirmation; eyes-free is not a reason to drop all checking. Long dictation meant to be edited later was never an eyes-free task. If an in-ear prompt cannot be heard, people will look anyway; the auditory channel fails on its own. Hard constraints in driving are a separate claim: there the issue is not cancelled value but a ban on requiring visual confirmation.
Applying it
- Use a short audible read-back or direct execution for low-risk commands; keep must-look confirms for high-cost actions.
- Offer repairs that do not require looking: respeak, spoken rejection, a cancel control on the wheel.
- Accept with gaze: from end of speech to the command taking effect, does the interface force the eyes onto the screen? If so, that command is not yet eyes-free.