WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: aria-hidden for content outside modal dialog?

for

From: Detlev Fischer
Date: Oct 17, 2015 1:39AM

Just for those wanting to experiment, here is another implementation of a dialog with background hidden using aria-hidden:
http://www.3needs.org/en/testing/code/role-dialog.html
While the focus cannot be trapped inside the dialog when traversing it with iOS / VoiceOver, aria-hidden ensures that the focus is set back to the triggering element once the dialog is closed.
The example is a couple of years old now and I haven't retested it with more recent browsers/AT.
Detlev

Am 17.10.2015 um 02:20 schrieb Jonathan Avila < <EMAIL REMOVED> >:

>> Element should not be exposed, unless it is focused or fires an
>> accessibility event.
>
> Steve, thanks for the clarification. This particular issue could still cause problems for users of assistive technology if strict focus management techniques are not used as my initial tests show inconsistent results with screen readers announcing the proper link text when aria-hidden is set to true on a link and you tab to it.
>
> Best Regards,
>
> Jonathan
>
> --
> Jonathan Avila
> Chief Accessibility Officer
> SSB BART Group
> <EMAIL REMOVED>
>
> 703-637-8957 (o)
> Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Steve Faulkner
> Sent: Friday, October 16, 2015 6:01 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] aria-hidden for content outside modal dialog?
>
> On 16 October 2015 at 22:05, Sailesh Panchang < <EMAIL REMOVED> >
> wrote:
>
>> You wrote: As a side note -- according to the ARIA spec aria-hidden
>> of true should be ignored by user agents and assistive technology when
>> applied to focusable content.
>> Please can you point me to the specs where it says so?
>
> It is not the case that it should be ignored when applied to a focusable element, but that the:
>
> Element should not be exposed, unless it is focused or fires an
>> accessibility event.
>
>
> Core Accessibility API Mappings 1.1
> http://www.w3.org/TR/core-aam-1.1/#details-id-94
>
>
>
> --
>
> Regards
>
> SteveF
> Current Standards Work @W3C
> <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;
> > > > > > >