WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Fourth rule of aria > aria-hidden

for

From: Jonathan Avila
Date: Jan 22, 2018 10:46AM

> I am primarily thinking of map components. A keyboard only user needs to be able to operate the map controls, but to a screen reader the map clutters up the page. Assuming there is an accessible alterantive to get text instructions or perform the primary function of the map,, isn't it valid (though not desireable) use of aria-hidden to hide the map and its controls from the screen reader user?

It is my understanding that the specifications indicate that browsers should expose focused aria-hidden content in the accessibility API in order to prevent nothing from being announced by screen readers.

Consider that there may be a number of people with low vision that can benefit from keyboard support and tex-to-speech. Skip links, landmarks, or other techniques can be used to allow screen reader users to skip past if they want. Seems like many screen readers will likely be using the browser cursor anyway and will encounter or pass the information as desired with those navigation commands.

Jonathan

Jonathan Avila
Chief Accessibility Officer
Level Access, inc. (formerly SSB BART Group, inc.)
<EMAIL REMOVED>
703.637.8957 (Office)
Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
Looking to boost your accessibility knowledge? Check out our free webinars!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Birkir R. Gunnarsson
Sent: Monday, January 22, 2018 7:11 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Fourth rule of aria > aria-hidden

What about content that cannot be made accessible toa screen reader, but still has to be oprable with the keyboard?
I am primarily thinking of map components. A keyboard only user needs to be able to operate the map controls, but to a screen reader the map clutters up the page. Assuming there is an accessible alterantive to get text instructions or perform the primary function of the map,, isn't it valid (though not desireable) use of aria-hidden to hide the map and its controls from the screen reader user?




On 1/22/18, Joshue O Connor - InterAccess < <EMAIL REMOVED> > wrote:
> Thats a good catch all :-)
>
> Josh
>
> Steve Faulkner wrote:
>> Have updated the 4th rule, thanks for feedback.
>>
>> https://w3c.github.io/using-aria/#fourth
>>
>> --
>>
>> Regards
>>
>> SteveF
>> Current Standards Work @W3C
>> <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-
>> w3c/>
>>
>> On 22 January 2018 at 09:36, Léonie Watson< <EMAIL REMOVED> > wrote:
>>
>>> On 22/01/2018 09:21, Fernand van Olphen wrote:
>>>
>>>> In this case aria-hidden="true" is used on the container div, and
>>>> the visible focusable element sits inside it. Is this also a
>>>> violation of the fourth rule?
>>>>
>>> It is, but the Using ARIA doc doesn't make this clear. I've filed an
>>> issue there, so hopefully we can get the 4th rule updated.
>>> https://github.com/w3c/using-aria/issues/32
>>>
>>> Léonie.
>>>
>>>
>>>
>>>> Kind regards,
>>>> Fernand van Olphen
>>>> Accessibility Advisor
>>>> Municipality of The Hague,
>>>> www.denhaag.nl<;http://www.denhaag.nl>;
>>>>
>>>> De disclaimer van toepassing op e-mail van de gemeente Den Haag
>>>> vindt u
>>>> op: http://www.denhaag.nl/disclaimer
>>>> >>>> >>>> archives at http://webaim.org/discussion/archives
>>>> >>>>
>>>>
>>> --
>>> @LeonieWatson @ <EMAIL REMOVED> Carpe diem
>>>
>>> >>> >>> archives at http://webaim.org/discussion/archives
>>> >>>
>> >> >> archives at http://webaim.org/discussion/archives
>> >
> --
> Joshue O Connor
> Director | InterAccess.ie
> > > archives at http://webaim.org/discussion/archives
> >


--
Work hard. Have fun. Make history.