RE: Accessible Testing Protocol for Mobile Website

Hi Mike, Phil et al.,

 

Just wondering if your comments/actions match to WCAG2, or any other generic
approach to accessibility?

 

There seems to be no coordinated approach to anything "accessible" at the
moment.

 

Should we not all coordinate around WAI?

 

If not, what are the alternatives?

 

VV best,

Howard

(Kent, UK).

 

 

  _____  

From: Mike Elledge [mailto:melledge@yahoo.com] 
Sent: 05 February 2015 17:55
To: Phill Jenkins; w3c-wai-ig@w3.org
Subject: Re: Accessible Testing Protocol for Mobile Website

 

Hi Phill--

 

Thank you for reminding us of the importance of context and use. Nothing is
as simple as it first seems in accessibility, is it?

 

I'm looking forward to seeing the mobile checker demo at CSUN. Will it
become available to the public? Any estimate of when that may be?

 

Mike

 

On Thursday, February 5, 2015 12:27 PM, Phill Jenkins <pjenkins@us.ibm.com>
wrote:

 

It is critical that we correctly frame the discussion, questions, and
responses.   

Yes WCAG can and should be used to frame the Mobile testing, but beyond that
we quickly need to distinguish between 
        mobile *web* testing 
        versus 
        mobile *native app* testing 
        and the overlap with 
        mobile *hybrid app* testing 

the other dimension to the framework is the platform, as in iOS, Android,
Windows, etc. 

For the old timers, this reminds me of the early days of Web accesibility in
the late 1990's during the browser wars and trying to support Windows,
Linux, OS/2, etc... 

Next phase will be tooling for improved *mobile testing* productivity.
Remember the early days with Bobby?   
For example, IBM has been demonstrating a mobile *native app* accessibility
checker. 
and IBM is already delivering on inclusive IBM Design Thinking early on
during the wireframe and front-end prototype phases of "mobile" projects. 
____________________________________________
Regards,
Phill Jenkins, 
IBM Accessibility