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

Re: Accessible Testing Protocol for Mobile Website

From: Gijs Veyfeyken <gijs@anysurfer.be>
Date: Fri, 6 Feb 2015 09:57:08 +0100
Message-Id: <0BD83AEB-EEB1-430F-918C-70189EA1BFEE@anysurfer.be>
To: W3C WAI Interest Group <w3c-wai-ig@w3.org>

The BBC's Standards and Guidelines for Mobile Accessibility might be helpful. 
http://www.bbc.co.uk/guidelines/futuremedia/accessibility/mobile <http://www.bbc.co.uk/guidelines/futuremedia/accessibility/mobile>

Kind regards,


Gijs Veyfeyken
AnySurfer - towards an accessible internet
Brussels - Belgium

> On 05 Feb 2015, at 22:10, Phill Jenkins <pjenkins@us.ibm.com> wrote:
> >. . . Just wondering if your comments/actions match to WCAG2 
> Yes absolutely!   
> Accessibility SME engineers have built initial spreadsheets* (a.k.a. the framework) that map the individual "native app* and *mobile web* testing procedures (checks) 
>         by WCAG 2.0 Level A and Level Double A Success Criteria (often multiple checks per success criteria) 
>         by platform and version (iOS, Android, and Windows desktop) 
>         by one of our three testing approaches: 
>                 AVT 1=semi automated using automated checking tools (which tool is part of the matrix), 
>                 AVT 2= with assistive technology (e.g VoiceOver, TalkBack, JAWS, etc.) 
>                 AVT 3=manual SME inspection (using tool bars, dev tools, effective simulators where appropriate, etc.) 
> the "coordinated approach" should be part of one of the WAI working group's charter, if not then it needs to be added, perhaps to the Evaluation & Repair Working Group. 
>         http://www.w3.org/WAI/eval/Overview.html <http://www.w3.org/WAI/eval/Overview.html> 
>           http://www.w3.org/WAI/ER/Overview.html <http://www.w3.org/WAI/ER/Overview.html> 
> Remembering I'm talking about testing at the end of mobile app development accessibility verification testing, as in conformance testing (a.k.a. complaince testing), not end user research with real people with disabilities used in evaluating design alternatives.  If you're not doing both during the app's life cycle, then you're only doing half the job. 
> * spreadsheets themselves and mapping to rules and algorythims are considered intellectual property. 
> ____________________________________________
> Regards,
> Phill Jenkins, 
> IBM Accessibility
Received on Friday, 6 February 2015 08:57:44 UTC

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