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

On 11/07/2016 13:10, Jonathan Avila wrote:
> FWIW.  I've seen on IE with Dragon cases where speaking text into an input field results in the value being programmatically set without keystrokes be fired.

Oh, interesting. I've just checked using 
https://patrickhlauke.github.io/touch/tests/event-listener-keyevents-text-input.html 
and indeed, once focus is in the text field, I can dictate letters (like 
"A", "B", "C" etc) but (with exception of explicit "PRESS SPACE" 
commands), the keydown/keyup JavaScript events that are being fired lack 
the necessary "key" property. When dictating entire words, only a single 
keydown and keyup event (again, missing any "key" property) are being 
fired. So you're right, even in these situations, Dragon isn't actually 
emulating a proper keyboard (only when explicitly doing things like 
"PRESS A, PRESS B, PRESS C")

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 12:23:01 UTC