A voice interface lets users communicate with a system through spoken language and receive spoken responses. It is valuable when hands-free operation matters, such as while driving or cooking, but noise, accents, and speech-recognition errors can quickly make the interaction frustrating. section 9.2.2 section 9.2.1
Treat voice as a limited, sequential channel rather than spoken text on a screen. Users cannot visually scan, reread, or skip long responses, so the interface should guide them clearly, maintain context, and keep replies brief and direct. section 9.2.2 section 9.2.4
Design voice interactions around manageable effort and recovery:
- Break tasks into incremental steps and let users confirm completion before continuing. section 9.2.4
- Handle misunderstandings with clarifying questions, repetition, and simplified responses rather than forcing users to restart. section 9.2.4
- Adjust speaking speed and pauses so users have time to process each response. section 9.2.4
- Confirm significant actions before executing them, especially when recognition errors could cause unintended results. section 9.2.4
- Offer multimodal support, such as links or visual aids, when spoken guidance alone is insufficient. section 9.2.4
From burdensome to usable
A long spoken explanation forces a driver to remember details they cannot scan. A better assistant gives one concise instruction, waits for confirmation, and asks a clarification question when background noise makes the command uncertain. section 9.2.2 section 9.2.4
Table 9.3 Modality overview
|
Text modality
|
Visual modality
|
Voice modality
|
Multimodal interactions
|
|
|---|---|---|---|---|
|
Description
|
Communication through written text
|
Communication using text with additional visual elements
|
Interaction via spoken language
|
Combines text, voice, and visual elements
|
|
Strengths
|
Precise communication.
Easy to reference.
|
Enhances comprehension with visuals through an engaging interface
|
Hands-free operation.
Natural conversational flow.
|
Richer user experience.
Versatile interaction.
|
|
Challenges
|
Typing can be slow.
May lack emotional tone.
|
Visuals may distract or be tuned out.
Requires a well-designed UI.
|
Requires clear speech.
Can misinterpret accents.
|
More complex to design and implement
|
|
When to use
|
In situations where typing is convenient
|
Scenarios needing visual aid for better understanding
|
Situations requiring hands-free interaction
|
Scenarios needing a combination of modalities
|
|
Effect on user engagement
|
High engagement in text-centric contexts
|
Improved engagement with visual aids
|
Increased engagement due to natural interaction
|
Enhanced engagement through diverse interaction modes
|
|
Evaluation techniques
|
User feedback surveys.
Usability testing.
|
User experience testing.
Visual effectiveness analysis.
|
Speech recognition accuracy tests.
User feedback.
|
A/B testing.
Multimodal usability assessments.
|
Compare voice with text, visual, and multimodal interaction to choose a channel based on hands-free needs, comprehension, and interaction complexity. section 9.2.1
