Re: Issue 59: not for WCAG 2.1?

On 31/01/2017 22:22, Gregg C Vanderheiden wrote:
>   It seems to me that….
> Unless you are going to build a keyboard into every web page that
> required anything more than clicks — there is no way for a WEB AUTHOR to
> ensure that everything can be done with a pointer.
>
> Mobile devices provide their own keyboards — but that is outside the
> purview of the web author.  They can’t see what type of keyboard is
> sending keystrokes to their web page.
>
> Am I missing something?

Possibly Note 1 of the SC

"Note 1: in most cases, the on-screen keyboard will already be provided 
by the operating system or user agent."

and most of the description, such as

"on mobile/tablet devices, the primary input mechanism is a touchscreen. 
While these devices do provide on-screen keyboards, generally these 
keyboards are only available to the user when focus is in an interface 
component that expects keyboard entry (such as a text input field). 
Moreover, these on-screen keyboards usually lack many of the keys 
available on regular physical keyboards (such as cursor keys, TAB, ESC).
If content is designed with the expectation that users can, at any given 
point, press a particular key or key combination, it will not be 
possible to operate the content in these situations."

?

> If not - then I think this needs to be dropped as out of scope for web
> page guidelines.

The requirement for authors would be not to simply implement key event 
listeners and call their site/app "keyboard accessible, so fine for all 
users" since that would make the site impossible to use for non-keyboard 
users?

Having said that, the fact that this affects more users than just PwD 
disproportionately, I'd be happy to retract this or defer to Silver.

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 Tuesday, 31 January 2017 23:49:50 UTC