ACTION-139 Add updates from conversation to voice and menu systems

This is an update of my October 1 revision of the  voice menus issue paper
[1]. My action was to add a few points based on our discussion during the
October 2 call [2]. The issue paper in the github repository doesn't seem to
include the October 1 revision. I think we should replace it with the
attached version, but we may want to discuss it in the group first. 

There were just a few points that needed to be updated from the October 2
call. 

 

Here's a summary of the changes in the attached revision.

 

1.       Under "Executive Function" 

"Limitations of executive function may also cause problems when the system
response is too slow. The user may not know whether their input has
registered with the system, and consequently may press the key or speak
again."

2.       A comment about the need for caution when recommending reserved
digits for specific functions.

"Other digits similarly could be used for specific reserved functions,
keeping in mind that too many reserved digits will be confusing and
difficult to learn. Remembering more than one or two reserved digits may be
problematic for some users. Addressing this with repeated verbal recitals of
the reserved digits to remind users of their functions will also be
distracting. 

3.       Added "adaptive voice systems" and "tapered prompts" to the section
on "technology solutions"

a. "Adaptive voice interface. This is a technology that is sensitive to the
user's behavior and changes the voice interface dynamically. For example, it
can slow down or speed up to match the user's speech rate.<a
href="http://cdn2.hubspot.net/hub/120925/file-59944739-pdf/documents/Adaptiv
e_Voice_WhitePaper.pdf">Adaptive Voice White Paper</a>"

b. "Tapered prompts. Good voice user interface design practices include
providing several different prompts for each point in the interaction. The
different prompts are used based on the users' behavior. For example, if the
user takes a long time to respond to a prompt, a simpler or more explanatory
version of the prompt by be used instead of the default."

 

I used the "[[" notation to refer to the VoiceXML references, but I wasn't
sure about the shortnames for those specs. I also wasn't sure how to refer
to links to non-W3C documents, so they are still full links.

 

Debbie

 

[1] original revision of voice menus issue paper
https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2015Oct/0003.h
tml

[2] discussion from October 2 call
https://www.w3.org/2015/10/02-coga-minutes.html