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 21:48, Patrick H. Lauke wrote:
> On 04/07/2016 21:27, Gregg Vanderheiden RTF wrote:

>> Right.  So what is the requirement on the Author?
>
> As with the existing WCAG 2.0 keyboard requirement as it stands, the
> other must NOT simply listen to mouseover/mouseenter/mousedown/mouseup,
> i.e. specific mouse events. In addition, they must NOT simply listen to
> touchstart/touchmove/touchend, i.e. touch-specific events. They must
> cater for keyboard and other non-pointer inputs.
>
> Now, and here's the tricky part: an author can currently satisfy WCAG
> 2.0 by explicitly listening to keydown/keyup/keypress events, which are
> specific to keyboard and keyboard-like interfaces (other inputs that, in
> essence, simulate/look like a keyboard to the OS/UA and send "faked"
> keyboard events). As certain input methods such as touch+AT do NOT send
> faked key events, authors can ALSO NOT rely on simply listening to
> keydown/keyup/keypress (in addition to whatever mouse/touch events
> they're also listening to anyway). They need to go one abstraction level
> higher and listen to focus/blur/click/contextmenu etc device/input
> agnostic events, as these are the only safe ones that are sent by all
> input modes (with some slight variations...in fact, in some scenarios,
> even focus/blur are not fired by all non-pointer inputs). And in doing
> this, they also get content that works for current traditional keyboards.

In fact, the current techniques 
https://www.w3.org/TR/WCAG20-TECHS/SCR2.html and 
https://www.w3.org/TR/WCAG20-TECHS/SCR35.html do exactly this (listen to 
generic "click"). These techniques would already satisfy the proposed 
rewording of the Guideline/SC.

The one technique that wouldn't conform is 
https://www.w3.org/TR/WCAG20-TECHS/SCR20.html which advocates use of 
keydown/keyup/keypress (though it then explains that this is not always 
necessary since the higher-level focus/blur/click are device/input 
agnostic).

So technique-wise, current WCAG almost already covers touch+AT. It's 
just the current wording of the Guideline/SCs, and the very specific 
https://www.w3.org/TR/WCAG20-TECHS/SCR20.html, which would either 
require a rewrite, OR a complete duplication of SCs.

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:06:10 UTC