W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2015

another example explaining why browsers need UAAG

From: Kim Patch <kim@redstartsystems.com>
Date: Thu, 30 Apr 2015 16:30:11 -0400
Message-ID: <554290D3.1030609@redstartsystems.com>
To: Jeanne Spellman <jeanne@w3.org>, User Agent Working Group <w3c-wai-ua@w3.org>

Here's the speech user example I promised earlier today:

Employees who use speech input to avoid exacerbating repetitive strain 
injuries need the ability to adjust keyboard shortcuts to make shortcuts 
consistent across browsers and other applications, and to replace single 
key shortcuts. While single key shortcuts increase efficiency for 
keyboard users, they are minefields for speech users because multiple 
commands can be accidentally tripped with a single phrase. These 
employees also need the ability to save and share these adjustments so 
it's possible to quickly and consistently set up a good default across 
computers and speech users.

Going further, employees who use speech input would experience a sea 
change if browser makers simply enabled multiple letter shortcuts, which 
would allow speech users to directly set keyboard commands that are 
appropriate for speech input rather than having to separately program 
speech macros to call keyboard shortcuts meant for keyboard users. For 
instance, a speech user might replace the key combination "Control++" 
with the six letters "zoom in" which is much easier for a speech input 
user to remember and pronounce.


Kimberly Patch
Redstart Systems, Inc.
(617) 325-3966

www.redstartsystems.com <http://www.redstartsystems.com>
- making speech fly

Blog: Patch on Speech
+Kim Patch
Twitter: RedstartSystems
www.linkedin.com/in/kimpatch <http://www.linkedin.com/in/kimpatch>
Received on Thursday, 30 April 2015 20:30:38 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 30 April 2015 20:30:38 UTC