E-mail List Archives
Re: Inaccessible mega menu and WCAG2
From: Patrick H. Lauke
Date: Jan 16, 2015 8:53AM
- Next message: Lynn Holdsworth: "Re: Inaccessible mega menu and WCAG2"
- Previous message: Lynn Holdsworth: "Re: Inaccessible mega menu and WCAG2"
- Next message in Thread: Lynn Holdsworth: "Re: Inaccessible mega menu and WCAG2"
- Previous message in Thread: Lynn Holdsworth: "Re: Inaccessible mega menu and WCAG2"
- View all messages in this Thread
On 16/01/2015 14:59, Jonathan Avila wrote:
> Mallory, I agree this makes perfect sense -- in practice we've had
> trouble fitting this into the menu/aria-expanded paradigm. One you
> indicate menu status as expand/collapse then activating the link to
> take you to another page no longer makes sense. In my opinion we are
> lacking a proper navigation paradigm in ARIA that would allow for
> this. We really need something like a button menu -- a composite
> control that can be activated directly and also has a pop up menu.
Would having a link (to the top-level page) followed by a discrete
secondary link (which acts as disclosure widget for the menu itself) be
problematic? I know it splits the functionality in two, but seems a fair
compromise to me (and for mouse interaction, make both open the menu on
hover)
P
--
Patrick H. Lauke
www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
- Next message: Lynn Holdsworth: "Re: Inaccessible mega menu and WCAG2"
- Previous message: Lynn Holdsworth: "Re: Inaccessible mega menu and WCAG2"
- Next message in Thread: Lynn Holdsworth: "Re: Inaccessible mega menu and WCAG2"
- Previous message in Thread: Lynn Holdsworth: "Re: Inaccessible mega menu and WCAG2"
- View all messages in this Thread