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

On 04/07/2016 22:12, David MacDonald wrote:
>>>If the webpage naively decided to handle its own keyboard control by listening to keypress or keydown events, then checking if the keycode
>
> so we'd be failing a <span tabindex="0" class="myclass" etc...
> role="button">fake button</span> when they have trapped keystroke 32 and
> 27 to mimic a button?

If they haven't also added a listener for click, yes (but they would 
have a click listener, as otherwise that fake button wouldn't work for 
mouse users either).

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, 4 July 2016 21:15:15 UTC