W3C home > Mailing lists > Public > wai-xtech@w3.org > November 2009

RE: Musings on ARIA role="application" blog post by Terrill Thompson

From: Schnabel, Stefan <stefan.schnabel@sap.com>
Date: Fri, 27 Nov 2009 12:36:02 +0100
To: Steven Faulkner <faulkner.steve@gmail.com>, W3C WAI-XTECH <wai-xtech@w3.org>
CC: "Keim, Oliver" <oliver.keim@sap.com>
Message-ID: <8EA44C66E2911C4AB21558F4720695DC5D867D2D2B@DEWDFECCR01.wdf.sap.corp>
Steve,

This is the reason why you can easily override the "forced mode switch" caused by role=application with new Jaws Navmode switches in Jaws 11.

The users who complain just have to have this update.

But this is a workaround, not the real thing. Blind Jaws users are also used to use Virtual mode as a last resort, because generally the web authors don't care about keyboard navigation.

The article presumes that web authors who have to implement keyboard navigation will either be lazy (supply none), non-standard (because there is none, only http://dev.aol.com/dhtml_style_guide which is still not "W3C official") or erroneous (everybody may miss something), and if so, Jaws Virtual Mode is the savior.

But honestly, what the world needs is 

a) A standardized Specification how to do Keyboard Navigation for/in Web Widgets authorized by W3C

b) An explicit checkpoint in WCAG 2.0+ to obey this specification

c) An Keyboard Navigation Consistency Checker for web authors

Too much in web accessibility (especially keyboard support) is still based on the goodwill of the authors.

The article also deals with something I call "the usability of accessibility and the expectation interest of users".

Jaws users are USED to a certain navigation paradigm, and if navigation by HEADING is NOT working in the application mode then either this needs to be supported in this mode or (as in Jaws 11) was worked around by having that dynamic mode switch.

I know also votings from the blind community that there should be as much as possible feature-equivalence between the two modes. Jaws has not implemented this so far, reasons unknown. But if so, it will make future musings obsolete and will just enhance the product.

Regards
Stefan


From: wai-xtech-request@w3.org [mailto:wai-xtech-request@w3.org] On Behalf Of Steven Faulkner
Sent: Freitag, 27. November 2009 10:29
To: W3C WAI-XTECH
Subject: Musings on ARIA role="application" blog post by Terrill Thompson

Musings on ARIA role="application"  blog post by Terrill Thompson
http://terrillthompson.com/2009/11/musings-on-aria-roleapplication.html
 
there should be discussion on the issues raised in this post. 
-- 
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html
Received on Friday, 27 November 2009 11:36:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:16:07 GMT