Re: Issue 59: not for WCAG 2.1?

  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?  

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


Gregg C Vanderheiden

> On Jan 31, 2017, at 3:00 PM, Andrew Kirkpatrick <> wrote:
> Issue 59 ( <>) has been proposed to be deferred for another time. As I see it, there are two ways that this can happen:
> No one does anything further with it, and it sits until we eventually say “I guess it is too late now…”
> We explicitly determine that it doesn’t fit into the WCAG 2.x model or for some other reason decide to defer it (defer might be to 2.1, silver, or tbd).
> My understanding is that this issue, which essentially requires that functionality can be operated with pointer inputs, is affecting all users and is not differentially having an adverse affect on users with disabilities. 
> I think that unless we can crisply define how to target an SC in a manner that specifically addresses issues that affect people with disabilities rather than “all touchscreen users” then we should defer it. Perhaps in Silver we will have an SC that speaks directly to multi-modal input for functionality and this will be addressed that way – after all, we will have an increasing number of interfaces (keyboard, voice, pointer, virtual gestures, etc) so perhaps if we aren’t starting from “make sure you have keyboard access” it will be more approachable.
> Thoughts?
> Thanks,
> Andrew Kirkpatrick
> Group Product Manager, Standards and Accessibility
> Adobe 

Received on Tuesday, 31 January 2017 23:42:25 UTC