W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2015

Re: Accessible Testing Protocol for Mobile Website

From: Mike Elledge <melledge@yahoo.com>
Date: Thu, 5 Feb 2015 17:54:30 +0000 (UTC)
To: Phill Jenkins <pjenkins@us.ibm.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <1093679436.355317.1423158870289.JavaMail.yahoo@mail.yahoo.com>
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?

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

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

Yes WCAG can and should beused to frame the Mobile testing, but beyond that we quickly need to distinguishbetween 
       mobile *web* testing
        mobile*native app* testing
        andthe overlap with
        mobile*hybrid app* testing

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

For the old timers, this reminds meof the early days of Web accesibility in the late 1990's during the browserwars 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 demonstratinga mobile *native app*accessibility checker.
and IBM is already delivering on inclusiveIBM Design Thinking early on during the wireframe and front-end prototypephases of "mobile" projects.
Phill Jenkins, 
IBM Accessibility

Received on Thursday, 5 February 2015 17:58:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:54 UTC