WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: JAWS and ARIA's application role

for

From: Léonie Watson
Date: Jul 6, 2011 11:57AM

"Has anybody else had problems with JAWS not entering application mode when
the role="application" attribute/value pair is not set on the body element,
but in an inner container?"

Having auto forms mode turned off has been known to cause a
conflict. Auto forms mode is turned on by default, but people sometimes turn
it off. Jaws effectively flips into forms mode when it encounters
role=application, to allow the keyboard commands to be passed back through.


Léonie.




--
http://tink.co.uk

Email: <EMAIL REMOVED>
Twitter: @LeonieWatson
Skype: Leonie.Watson

-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Ney André de
Mello Zunino
Sent: 06 July 2011 14:06
To: WebAIM Discussion List
Subject: [WebAIM] JAWS and ARIA's application role

Hello.

Has anybody else had problems with JAWS not entering application mode when
the role="application" attribute/value pair is not set on the body element,
but in an inner container? I have a page which should work in document mode
until an ARIA widget receives focus. This ARIA widget is within a container
div with role="application" set. However, keystrokes continue to be
intercepted by the screen reader, instead of being left to the application.
Setting the role on the body element results in the expected behavior.


DOESN'T WORK

<body>
...
<div role="application">
...ARIA widget...
</div>
...
</body>


WORKS

<body role="application">
...
...ARIA widget...
...
</body>


Thank you in advance,

--
Ney André de Mello Zunino
Pesquisa e Desenvolvimento
Softplan/Poligraph
Sistema da Qualidade Certificado ISO9001:2008
Fone/Fax: 0xx(48) 3027-8000
http://www.softplan.com.br/