WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Headings in a Menu Button UI pattern

for

From: Birkir R. Gunnarsson
Date: Jun 9, 2015 9:05AM

Adobe decided to avoid the menu role for its accessible megamenu implementation:
https://adobe-accessibility.github.io/Accessible-Mega-Menu/
(it is good, ehough they should have implemented the escape key to
close a menu and move focus back to its trigger element).
You can use group labels and focusable separators inside menus, though
assistive technology support for that is, shall we say, more of a
future proposition rather than today's reality.

I think if you have more than two items with a common label, and you
want to go with a menu construct, group the items into a submenu with
an appropriate triggering element and keyboard navigation (arrow keys
to open and close), or equivalent for touch-screen.
It would simplify keyboard operation as well as provide grouping and a
common label within the context of menus, something users of menus on
operating systems are used to.
Once properly supported, the concept of menus within webpages and apps
can be useful, but today there are technical challenges, such as
functions on mobile devices with assistive technologies, that create
potential barriers.
Cheers
-B


On 6/9/15, Moore,Michael (HHSC) < <EMAIL REMOVED> > wrote:
> Have you spoken to Hixie?
>
> Mike Moore
> Accessibility Coordinator
> Health and Human Services Commission
> Civil Rights Office
> (512) 438-3431 (Office)
> (512) 574-0091 (Cell)
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
> Of Jim Allan
> Sent: Tuesday, June 09, 2015 9:35 AM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] Headings in a Menu Button UI pattern
>
> too bad we don't the the <lh> element from HTML3
> http://www.w3.org/MarkUp/html3/listheader.html
>
> always thought it would be useful. The description sounds much like
> <details> and <summary>
>
> though just having some kind of "title" or "caption" or "heading" for a
> list like we do for table-caption and images-figure/figcaption would be
> useful.
>
> <ul>
> <lh>Fruits I Like:<lh>
> <li>Apples</li>
> <li>Bananas</li>
> <li>Oranges</li></ul>
>
>
>
> On Tue, Jun 9, 2015 at 6:43 AM, Marco Zehe < <EMAIL REMOVED> > wrote:
>
>> OK, for that case an additional suggestion: Each of the elements
>> inside reacts to the Escape key which a) closes the navigation menu
>> and b) sets focus back to the button that opened it.
>>
>> Marco
>>
>>
>> 2015-06-09 12:19 GMT+02:00 _mallory < <EMAIL REMOVED> >:
>>
>> > On Tue, Jun 09, 2015 at 12:12:45PM +0200, Marco Zehe wrote:
>> > ...
>> > > 3. Or if it is not possible to insert the items in the DOM at that
>> point,
>> > > make sure after setting the visibility to true, to set focus on
>> > > the
>> first
>> > > item within that account navigation block, since it can be assumed
>> > > the
>> > user
>> > > wants to interact with this now.
>> >
>> > Here we have a difference between users: while a screen reader user
>> > might "be assumed to want to interact with this now", for a sighted
>> > keyboarder it's often just "what is here?". Having my focus moved
>> > into things I only wanted to quick see what was there so then
>> > needing to shift-tab out each time isn't fun.
>> >
>> > Though I'm a lazy user and this is just my opinion.
>> >
>> > _mallory
>> > >> > >> > archives at http://webaim.org/discussion/archives
>> > >> >
>> >> >> archives at http://webaim.org/discussion/archives
>> >>
>
>
>
> --
> [image: http://www.tsbvi.edu] <http://www.tsbvi.edu>;Jim Allan, Accessibility
> Coordinator & Webmaster Texas School for the Blind and Visually Impaired
> 1100 W. 45th St., Austin, Texas 78756
> voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/
> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
> > > http://webaim.org/discussion/archives
> > > > > >


--
Work hard. Have fun. Make history.