WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Dialog semantics and aria?

for

From: Greg Kraus
Date: Apr 25, 2014 12:33PM

The problem with role="dialog" and role="document" has to do with the
difference in how certain screen readers handle application mode.
Namely, older versions of NVDA would not let you use the virtual
cursor at all in role="dialog". In that case it became necessary to
also use role="document" to allow NVDA users to use their virtual
cursor. The latest version of NVDA (2014.1) does not have this
problem.

You can read about the situation here.

http://accessibility.oit.ncsu.edu/blog/2014/01/02/incredible-accessible-modal-window-version-2/

Greg
--
Greg Kraus
University IT Accessibility Coordinator
NC State University
919.513.4087
<EMAIL REMOVED>
http://go.ncsu.edu/itaccess

On Fri, Apr 25, 2014 at 2:29 PM, Jesse Hausler < <EMAIL REMOVED> > wrote:
> With regards to accessible semantics and aria, would you consider a panel
> that pops up and fills the entire screen, with say a form.. the same as a
> modal overlay? Once the panel is closed, focus goes back to the trigger
> page.
>
> We do this quite a bit for mobile apps. I see them as the same, but would
> like to hear other opinions.
>
> Jesse
>
>
>
>
> On Fri, Apr 25, 2014 at 11:06 AM, Jesse Hausler < <EMAIL REMOVED> >wrote:
>
>> For the landmark-ness of it? :)
>>
>>
>> On Fri, Apr 25, 2014 at 11:02 AM, Bryan Garaventa <
>> <EMAIL REMOVED> > wrote:
>>
>>> >I got a tip from some folks at CSUN to embed a div with role="document"
>>> to
>>> address the issue with screen readers and application mode that you
>>> mention.
>>> Have you found luck with that method?
>>>
>>> It's true that the document role negates applications mode, but it then
>>> begs
>>> the question, why use the dialog role if you are only then negating it?
>>> :)
>>>
>>>