WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: SC 2.1.2: Leave, but to where?

for

From: Birkir R. Gunnarsson
Date: Nov 29, 2020 4:11PM

I would explain the usability issue with the menu construct, saying
that while technically it passes accessibility it requires a lot of
scripting overhead for developers and causes a lot of confusion for
screen reader users.
Recommend that instead you construct accordion/navigation constructs
(very minor Javascript for developers, easy and intuitive navigation
for screen reader users).


On 11/29/20, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
> On 29/11/2020 19:08, <EMAIL REMOVED> wrote:
> [...]
>> Is this a violation of SC 2.1.2?
>
> Strictly, no, as there *is* a way to leave the component you were in.
>
> As noted, this is likely the difference between being in browser vs
> forms mode. That's not something authors have control over directly.
>
> > As a SR user I don't like menus for navigations at all, but this is
> because
> > I never found an example causing no problems.
>
> And arguably ARIA-style menus should not be used for regular navigation,
> but for application-like menus. But that's been a long ongoing
> discussion even among WCAG/ARIA folks...
>
> https://github.com/w3c/aria-practices/issues/353
>
> 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.