Re: Perhaps we can follow the LVTF and close a few of our proposals

I strongly support keeping this one. This is also a problem I've been 
trying to fight in various guises as well, some firmly in the 
accessibility area.

There's been a long history of focus issues with folks using a 
combination of speech and keyboard. And Google doc menus are not 
compatible with mouseless browsing tools because the keystrokes used by 
those tools are conscripted by Docs.

I think it's going to be increasingly important going forward for 
developers to think more about the use of multiple input methods that 
aren't aware of each other. The combination of speech and pointer is a 
particularly powerful and enabling one for folks with mobility issues.

Encouraging developers to think AND instead of OR also makes the 
importance of user customization more obvious in areas where the needs 
of the different input methods might clash (e.g. single key shortcuts 
work well for keyboard users but spell disaster for speech users).

Cheers,
Kim

On 12/9/2016 6:16 AM, Patrick H. Lauke wrote:
> On 09/12/2016 02:22, David MacDonald wrote:
>
>
>> - Issue 64 Concurrent Input Mechanisms
>> https://github.com/w3c/wcag21/issues/64
>> <https://github.com/w3c/wcag21/issues/64>
>
> I'm fairly neutral on this one. It IS a problem (and one I've been 
> trying to fight in various guises, such as in my presentations where I 
> try to drum it into developers to stop thinking about touch OR mouse 
> OR keyboard and to instead think about touch AND mouse AND keyboard), 
> but I can see the argument that it's not one that burdens users with 
> disabilities significantly more than all other users, so mostly a 
> problem of usability/UX.

-- 
___________________________________________________

Kimberly Patch
President
Redstart Systems
(617) 325-3966
kim@redstartsystems.com <mailto:kim@redstartsystems.com>

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

Blog: Patch on Speech
+Kim Patch
@RedstartSystems
www.linkedin.com/in/kimpatch <http://www.linkedin.com/in/kimpatch>
___________________________________________________