WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Fourth rule of aria > aria-hidden

for

From: Birkir R. Gunnarsson
Date: Jan 22, 2018 5:21AM

And this is why I have interpreted the 4th rule of ARIA such that
aria-hidden is allowed on elements containing focusable elemnts, while
not allowed on the focusable elements directly.
We all know aria-hidden is dangerous, and warning against frivolous
use is important, bt there, as I see it, legitimate use cases for it,
this being one of them.


On 1/22/18, Steve Green < <EMAIL REMOVED> > wrote:
> I agree. We encounter this a lot with third-party plug-ins for maps,
> interactive charts and all sorts of other features for which accessible
> alternatives are provided on the same page. These are often
> keyboard-accessible but not screen reader accessible.
>
> Steve
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
> Of Birkir R. Gunnarsson
> Sent: 22 January 2018 12:11
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> 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.
> > > http://webaim.org/discussion/archives
> > > > > >


--
Work hard. Have fun. Make history.