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

RE: If you use the WAI-ARIA role "application", please do so wisely!

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Thu, 9 Feb 2012 09:17:06 -0500
Message-ID: <d3107eb9f6f9159270f208276746e27f@mail.gmail.com>
To: w3c-wai-ig@w3.org
I have personally seen issues with the use of role=”dialog” and
role=”application” in particular on simulated dialogs.   While technically
the specification allows for the use of the document role within the
application or dialog role in practice  I’ve found this does not work well
with different screen readers and across browsers.   Most simulated dialog
content is not simply buttons but often form fields with other on-screen
text and instructions that may need to be access with the virtual cursor.
While the use of aria-describedby can assist with some of this use of the
virtual cursor is still very important to users in quickly navigating and
reviewing spelling.



Jonathan



*From:* Ian Sharpe [mailto:isforums@manx.net]
*Sent:* Thursday, February 09, 2012 4:48 AM
*To:* accessible@googlegroups.com
*Cc:* 'free-aria'; w3c-wai-ig@w3.org; 'WebAIM Discussion List'
*Subject:* RE: If you use the WAI-ARIA role "application", please do so
wisely!



Hi Dominic



I've used the ARIA role="application" on the body element of a web page in
which I want all control of the keyboard handled by the page itself, not
the screen reader. This works perfectly on FF and IE using NVDA, but Chrome
just ignores it and NVDA continues to handle keyboard events.



Can you confirm that Chrome does implement this role correctly and expose
the necessary information to screen readers? I believe NVDA doesn't have
such good support for the web-kit browsers and particularly Chrome, as it
does for FF and IE, but also believe this is in part because Chrome is a
little behind these browsers in exposing the necessary information.



Cheers

Ian




------------------------------

*From:* accessible@googlegroups.com [mailto:accessible@googlegroups.com] *On
Behalf Of *Dominic Mazzoni
*Sent:* 08 February 2012 15:52
*To:* accessible@googlegroups.com
*Cc:* free-aria; w3c-wai-ig@w3.org; WebAIM Discussion List
*Subject:* Re: If you use the WAI-ARIA role “application”, please do so
wisely!

Marco's advice on using role=application is good, but note that Gmail
doesn't actually use role=application. The underlying Gmail problem
reported in this article looks like a new bug that only affects
NVDA+FIrefox, when Gmail's keyboard shortcuts are enabled. If you use
JAWS+Firefox, NVDA+IE, or if you switch off Gmail's keyboard shortcuts,
everything works as it did before. We're still investigating why
NVDA+Firefox behaves differently.



- Dominic

On Mon, Feb 6, 2012 at 11:46 AM, Kevin Chao <kevinchao89@gmail.com> wrote:

Marco Zehe, Hamburg, Germany, Mozilla a11y QA.
wrote up this great, informative, and practical: New blog post: If you
use the WAI-ARIA role "application", do so wisely!
http://www.marcozehe.de/2012/02/06/if-you-use-the-wai-aria-role-application-please-do-so-wisely/
#a11y #aria #axs

Kevin

--
You received this message because you are subscribed to the Google Groups
"accessible" group.
To post to this group, send email to accessible@googlegroups.com.
To unsubscribe from this group, send email to
accessible+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/accessible?hl=en.



-- 
You received this message because you are subscribed to the Google Groups
"accessible" group.
To post to this group, send email to accessible@googlegroups.com.
To unsubscribe from this group, send email to
accessible+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/accessible?hl=en.
Received on Thursday, 9 February 2012 14:17:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 9 February 2012 14:17:38 GMT