WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: what roles will make a pop up dialog work

for

From: Nancy Johnson
Date: Oct 8, 2014 4:30AM

'When using aria-hidden="false" on a container that includes style="none",
JAWS will now expose this to users even though it is
visually hidden from sighted users.''

'Apologies, this is confirmed in IE11 using JAWS15, even though it is not
supported elsewhere that I'm aware of.'

That is too bad as we might have added it to legacy sites that we developed
and maintain. There is no funding to check and change. I hope it doesn't
change in other browsers.

Nancy

On Tue, Oct 7, 2014 at 7:44 PM, Bryan Garaventa <
<EMAIL REMOVED> > wrote:

> Apologies, this is confirmed in IE11 using JAWS15, even though it is not
> supported elsewhere that I'm aware of.
>
> -----Original Message-----
> From: <EMAIL REMOVED> [mailto:
> <EMAIL REMOVED> ] On Behalf Of Bryan Garaventa
> Sent: Tuesday, October 07, 2014 4:42 PM
> To: 'WebAIM Discussion List'
> Subject: Re: [WebAIM] what roles will make a pop up dialog work
>
> Also, as a quick note regarding aria-hidden, there are some changes to be
> aware of for the future.
>
> When using aria-hidden="false" on a container that includes style="none",
> JAWS will now expose this to users even though it is
> visually hidden from sighted users.
>
> This is especially important to keep in mind for dynamic tab panels,
> dialogs, popups, menus, and any other form of dynamic content
> if aria-hidden is used incorrectly.
>
>
>
> -----Original Message-----
> From: <EMAIL REMOVED> [mailto:
> <EMAIL REMOVED> ] On Behalf Of Bryan Garaventa
> Sent: Tuesday, October 07, 2014 4:07 PM
> To: 'WebAIM Discussion List'
> Subject: Re: [WebAIM] what roles will make a pop up dialog work
>
> If this is a modal, the simplest way is to use the focus() method to set
> focus to the beginning of the dialog region, and use
> aria-hidden on each of the firstChild nodes in the body excluding the
> dialog div, so that the back ground is hidden from screen
> reader users. This way you will only see the modal content and none of the
> background content. Then simply confine keyboard focus
> within the active elements in the dialog, and provide a method to close
> it. When closed set focus back to the triggering element,
> and set all previously set aria-hidden attributes to 'false'.
>
> If this is a simple dialog and you don't want to hide the background
> content, the focus() method should set focus to the beginning
> of the dialog content.
>
> You can use role=dialog or role=alertdialog, but keep in mind this will
> restrict initial keyboard focus to only active elements
> using NVDA until it is aborted.
>
>
> -----Original Message-----
> From: <EMAIL REMOVED> [mailto:
> <EMAIL REMOVED> ] On Behalf Of Lucy Greco
> Sent: Tuesday, October 07, 2014 2:50 PM
> To: WebAIM Discussion List
> Subject: [WebAIM] what roles will make a pop up dialog work
>
> hello:
> i should know the answer to this but its confusing me.
> i have a client that is wanting a pop up dialog of information and links
> to come up when a link is clicked, and then letting it be
> dismissed and for it to go a way.
>
> currently the dialog information is beeing added to the dom at the bottom
> and the dismiss is working but its not constraining or
> even focusing on the information in the dialog. a user that has used it
> might know to go to the bottom of the page but ideally
> they should be drawn to
> it and kept with in the dialog until its dismist can some one remind
> me what the proper codeing to do this is thanks lucy Greco Web
> Accessibility Evangelist IST - Architecture, Platforms, and
> Integration University of California, Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
> > > messages to <EMAIL REMOVED>
>
> > > messages to <EMAIL REMOVED>
>
> > > messages to <EMAIL REMOVED>
>
> > > >