WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: 2.4.7 or 2.1.1 on "hidden" submenu elements?

for

From: Birkir R. Gunnarsson
Date: May 7, 2020 5:59AM

I've reported this under 2.4.3 in the past, though internally I don't
attach WCAG success criteria to issues.
I think it's a bit of a gap in WCAG, one which could be addressed with
either a new one or clearer language around one of the 3 candidates.


On 5/6/20, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
> On 06/05/2020 21:44, Jared Smith wrote:
>> I think it's clearly a 2.4.7 (focus visible) error, but I'd fail under
>> 2.1.1 also. This states "All functionality of the content is operable
>> through a keyboard interface..." and I think it's very hard to argue
>> that the "functionality" (defined as "processes and outcomes") is
>> actually "operable" using a keyboard if a keyboard user has no idea
>> what the keyboard interactions are doing. Saying it passes 2.1.1 would
>> be like saying a video passes captioning requirements when the
>> captions are there, but totally transparent and invisible, or like
>> saying sufficient alternative text is present, when it is hidden from
>> screen reader users.
>
> If there is a keyboard-operable way to open/close the fake menus
> visually too, to me that would swing it more towards a pass of 2.1.1.
> But if there isn't, then yes feels like 2.1.1 would be appropriate
> failure (I'd fail for the lack of ability to open the menus).
>
> I'd also throw 2.4.3 Focus Order into the mix, as when the menus are
> closed, the focus should not jump into the hidden things (though one
> COULD argue that the order is still logical in a sense).
>
> P
> --
> Patrick H. Lauke
>
> https://www.splintered.co.uk/ | https://github.com/patrickhlauke
> https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > > >


--
Work hard. Have fun. Make history.