WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: what roles will make a pop up dialog work

for

From: Greg Gamble
Date: Oct 9, 2014 1:50PM

" Developers should never include ARIA attributes within markup even if set to 'false' unless there is a specific purpose to do so, because the inclusion of the state/property may unexpectedly alter the feedback for AT users simply by being present."

Thanks ... this simplifies things actually.


Greg
SBCTC

-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Bryan Garaventa
Sent: Thursday, October 09, 2014 11:21 AM
To: 'WebAIM Discussion List'
Subject: Re: [WebAIM] what roles will make a pop up dialog work

That's right, in the same way that aria-expanded='false' and aria-pressed='false' and aria-checked='false' impart specific functionality that is not included when the attribute is undefined by not being present.

Developers should never include ARIA attributes within markup even if set to 'false' unless there is a specific purpose to do so, because the inclusion of the state/property may unexpectedly alter the feedback for AT users simply by being present.


-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Jonathan Avila
Sent: Thursday, October 09, 2014 11:10 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] what roles will make a pop up dialog work

[Jesse wrote]
> Plus isn't aria-hidden implied to be false by default?

This is one of the differences between ARIA properties and HTML properties such as hidden, required, disabled etc. You cannot explicitly set these HTML properties to false -- by simply including the attribute they equate to true. ARIA Boolean properties can expressly be set to true or false. I imagine this was done in ARIA to indicate instances where something clearly needed to be indicated but it might not be clear through native semantics without ARIA.

Jonathan

-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Bryan Garaventa
Sent: Thursday, October 09, 2014 1:57 PM
To: 'WebAIM Discussion List'
Subject: Re: [WebAIM] what roles will make a pop up dialog work

That's correct, which is intended to be a feature that addresses offscreen text that doesn't require the use of CSS. See
https://bugzilla.mozilla.org/show_bug.cgi?id=945194

-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Jesse Hausler
Sent: Wednesday, October 08, 2014 7:06 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] what roles will make a pop up dialog work

Are you saying that a div like this.. .

<div aria-hidden="false" style="displayNoneStyle"> stuff </div>

Will be readable with jaws? that's silly.

display:none should display:none...

Plus isn't aria-hidden implied to be false by default?

On Wed, Oct 8, 2014 at 3:30 AM, Nancy Johnson < <EMAIL REMOVED> > wrote:

> '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
> > > > > > list messages to <EMAIL REMOVED>
> >
> > > > > > list messages to <EMAIL REMOVED>
> >
> > > > > > list messages to <EMAIL REMOVED>
> >
> > > > > > list messages to <EMAIL REMOVED>
> >
> > > list messages to <EMAIL REMOVED>
>