WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Fourth rule of aria > aria-hidden

for

From: Patrick H. Lauke
Date: Jan 22, 2018 5:45AM

The rule, in essence, says: you don't want an AT user setting focus to
"nothing", as they're left wondering what they just set focus to. If
it's aria-hidden (or contained inside an aria-hidden container), but
received focus, it's an empty step in the focus cycle.

Nobody dies when this happens, to be clear. And the "rules" of using
ARIA are more good practice maxims, not hard failures.

IF you can justify why something still receives keyboard focus but isn't
announced at all to AT users, cool.

P

On 22/01/2018 12:21, Birkir R. Gunnarsson wrote:
> 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
>>
>>