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

1. How will users handle their AT not working as they expect it to?

 

AT, eg JAWS, needs to provide better messaging just like they do for
other controls through INSERT+F1 or tutor messages.

Users, on other hand, need to educate themselves and use the help
resources provided.

 

 

2. Will web application developers do a satisfactory job of providing
keyboard and non-visual access to their applications, so that the usual
AT keystrokes

truly aren't necessary?

 

It depends. Building keyboard support for complex applications is tricky
and should be avoided where traditional alternatives exist.

 

3. Will web applications be built using standard keyboard interfaces, so
users don't have to memorize a different set of keystrokes for every
online application they encounter?

 

This has come up on a number of accessibility lists. IMHO, we should
first strive to provide basic keyboard navigation, eg use left/right
arrow keys to navigate between tabs of atab pannel, before worrying
about control+tab to switch between them.

 

Just my two cents.

Victor

 

From: wai-xtech-request@w3.org [mailto:wai-xtech-request@w3.org] On
Behalf Of Steven Faulkner
Sent: Friday, November 27, 2009 1:29 AM
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
<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