E-mail List Archives

Re: Mega menus - Headings or no heading?


From: Maxability
Date: Oct 19, 2017 2:45AM


I assume you want to provide headings within the menu to differentiate sections within the mega menu. I think the menu and menuitem roles already provide that differentiation.
Thanks & Regards

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Birkir R. Gunnarsson
Sent: Wednesday, October 18, 2017 1:51 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Mega menus - Headings or no heading?

For the bonus question.
If you are using the whole menu/menuitem roles, you can't have headings inside the menu (the menuitem role overrides any semantic inside it).
As for the first question, I would just mak it a utton. The user basically is not able to see the menu except when it is open, so the page is almost nev;er in a state where a heading is particularly useful.
There is no harm in putting it in a heading, but there is also limited benefit.

On 10/17/17, Jordan Wilson < <EMAIL REMOVED> > wrote:
> Quick inquiry about Navigation buttons that open a mega menu.
> For example, 3 buttons each of which opens a large section of
> navigation options.
> Should they be headings or not? (assuming everything else is correct
> from an a11y standpoint)
> Headings introduce the content that follows, but technically a menu is
> introducing navigation and not content. I have looked around at some
> popular accessible sites and it seems to be 50/50. Some folks make the
> button an H1, some an H2 (even though its above the main H1 in the
> DOM) and some do not make it a heading at all.
> Opinions wanted.
> Also, an extra credit question:
> If the mega menu itself has headings inside it, does that change your
> opinion at all?
> Thanks,
> Jordan
> > > archives at http://webaim.org/discussion/archives
> >

Work hard. Have fun. Make history.