E-mail List Archives
Re: Inaccessible mega menu and WCAG2
From: Lynn Holdsworth
Date: Jan 16, 2015 8:36AM
- Next message: Patrick H. Lauke: "Re: Inaccessible mega menu and WCAG2"
- Previous message: Jonathan Avila: "Re: Inaccessible mega menu and WCAG2"
- Next message in Thread: Patrick H. Lauke: "Re: Inaccessible mega menu and WCAG2"
- Previous message in Thread: Jonathan Avila: "Re: Inaccessible mega menu and WCAG2"
- View all messages in this Thread
Thanks everyone.
No, it's not possible to open the menu or get to a different
destination by activating one of the links in the top menu.
2.1.1 looks like a good point to fail it on - thanks Patrick.
I worked on a menu system for a while, and it functioned pretty much
exactly like native menus: left/right arrows move across the top or
open/close sub-submenus; down arrow opens a submenu or moves through
its options; Esc closes a submenu, etc., and I liked it a lot. But it
wasn't possible to create an implementation that worked across all
screenreaders. And we were never sure whether we should indicate that
an item could be expanded if pressing Enter moved the user to a
different page. So I'm very interested in this discussion and what you
all think.
Best, Lynn
On 16/01/2015, Don Mauck < <EMAIL REMOVED> > wrote:
> I'd like to give my two cents for what it's worth. For me, I like the way
> menus and submenus currently work as it is the way most application menus
> work.
>
>
- Next message: Patrick H. Lauke: "Re: Inaccessible mega menu and WCAG2"
- Previous message: Jonathan Avila: "Re: Inaccessible mega menu and WCAG2"
- Next message in Thread: Patrick H. Lauke: "Re: Inaccessible mega menu and WCAG2"
- Previous message in Thread: Jonathan Avila: "Re: Inaccessible mega menu and WCAG2"
- View all messages in this Thread