W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2014

Q: Time Limit Methods for Native Mobile

From: Julie Romanowski <julie.romanowski.l87g@statefarm.com>
Date: Tue, 18 Nov 2014 16:57:13 +0000
To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <2F9CDEEFC09F2B4DA143BE00C8AA4EB1440AA38D@WPSDGQH7.OPR.STATEFARM.ORG>
I’m trying to get some clarification before meeting with a developer to discuss accessibility needs for a native mobile application for Android. Per WCAG 2.0 Level A 2.2.1 Timing Adjustment (http://www.w3.org/TR/WCAG20/#time-limits-required-behaviors), a method must be provided to extend, change or turn off time limits. The developer is relying on the system alert (banner) to notify the user, and believes that this meets the requirement. A couple of my accessibility resources argue that this method does not meet 2.2.1 requirements, and feel that the developer should use an alert dialog within the application.



While the method the developer is using does not follow any of the listed techniques for 2.2.1, the method does appear to allow the user to adjust the time limit by accessing the notification bar in Android. Seeing as WCAG requirements can be met using techniques other than those listed in W3C's Techniques for WCAG 2.0 document, would relying on the Android banner be an acceptable way to conform?



I want to be sure that I’m addressing an actual Level A violation, not just a best practice issue, and would appreciate any input this group could provide.




Julie Romanowski
Senior ICT Accessibility Specialist
Digital Accessibility, State Farm®
office: 309-735-5248
mobile: 309-826-8196

"Life's most persistent and urgent question is, 'What are you doing for others?'" ~ Dr. Martin Luther King Jr.
Received on Tuesday, 18 November 2014 16:57:43 UTC

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