E-mail List Archives
Re: Inaccessible mega menu and WCAG2
From: Patrick H. Lauke
Date: Jan 16, 2015 9:12AM
- Next message: Patrick H. Lauke: "Re: Inaccessible mega menu and WCAG2"
- Previous message: Lynn Holdsworth: "Re: Inaccessible mega menu and WCAG2"
- Next message in Thread: Patrick H. Lauke: "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 16:06, Lynn Holdsworth wrote:
> I think having two links might be confusing for screenreader users,
> especially if the text on both links says the same thing.
Of course, the text must be different - also, I said links but in fact I
should have said button (with appropriate aria-expanded, aria-controls,
etc), my fault. Was thinking something like...
<ul>
<li><a href="...">About</><button aria-expanded="false"
aria-controls="aboutmenu" aria-haspopup="true">About menu</button>
<ul id="aboutmenu" ...>
...
</li>
...
</ul>
with the button visually hidden by default, but made visible (perhaps
just as a discrete icon) on focus...
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: Patrick H. Lauke: "Re: Inaccessible mega menu and WCAG2"
- Previous message: Lynn Holdsworth: "Re: Inaccessible mega menu and WCAG2"
- Next message in Thread: Patrick H. Lauke: "Re: Inaccessible mega menu and WCAG2"
- Previous message in Thread: Lynn Holdsworth: "Re: Inaccessible mega menu and WCAG2"
- View all messages in this Thread