Re: Proposal: expanding/modifying Guideline 2.1 and its SCs (2.1.1, 2.1.2, 2.1.3) to cover Touch+AT

Just as an additional data point here, as I'm still working on 
untangling/generalising this:

For the first time today, I've been playing with Dragon 
NaturallySpeaking. Using my test page 
https://patrickhlauke.github.io/touch/tests/event-listener-keyevents.html 
I've confirmed that when using direct command like "CLICK test button", 
Dragon does exactly what I'd expected it to - it simply sets the focus 
on the button and clicks it, without sending any faked TAB key or ENTER 
key etc. In short, however we want to shape this (either modifying the 
existing keyboard guidelines, modifying the definition of "keyboard", or 
making new SCs) this will also apply to speech input like Dragon's.

(Of course, another way of navigating with Dragon is to issue "TAB", 
"TAB", "ENTER" commands, but in those scenarios Dragon is quite clearly 
a keyboard / emulates an actual keyboard, so existing SCs apply).

P
-- 
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke

Received on Monday, 11 July 2016 10:46:12 UTC