W3C home > Mailing lists > Public > public-html-a11y@w3.org > January 2014

Re: is role=menubar NOT for navigation menus.

From: Jason Kiss <jason@accessibleculture.org>
Date: Wed, 15 Jan 2014 15:01:18 +1300
Message-ID: <CACFCJLRGBeaVDP9P9C+bzj+169Z=uO_3iaGbjk8LAiaA6sJ7_A@mail.gmail.com>
To: David MacDonald <david100@sympatico.ca>
Cc: Richard Schwerdtfeger <schwer@us.ibm.com>, Janina Sajka <janina@rednote.net>, HTML Accessibility Task Force <public-html-a11y@w3.org>, kirsten@can-adapt.com
Hi,

I'd suggest looking at this implementation instead of the wet-boew one as
it's a little more recent and its keyboard interaction is a little more
robust, although it's still based on wet-boew work:

http://canada.ca/en/index.html

Personally, I think this is a reasonable use of role="menubar", and not
inconsistent with the definition of menu/menubar in the ARIA spec or the
authoring practices document.

Rich?

Cheers,

Jason


On Wed, Jan 15, 2014 at 1:26 PM, David MacDonald <david100@sympatico.ca>wrote:

> Hi Rich
>
>
>
> Now just to be rock solid sure I understand ...If your NAV menu example
> below was a JavaScript dropdown (on mouseover, or keyboard focus) Like the
> main nav menu at the top of this page
> http://wet-boew.github.io/wet-boew/demos/index-en.html
>
> you would still not recommend role=menubar, right?
>
>
>
> the ARIA best practices DOC, which talks about links...
>
> http://www.w3.org/TR/wai-aria-practices/#menu
>
> thatís what confused me
>
>
>
> Cheers,
>
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613.235.4902
>
> http://ca.linkedin.com/in/davidmacdonald100
>
> www.Can-Adapt.com <http://www.can-adapt.com/>
>
>
>
> *Sent:* January 14, 2014 6:28 PM
>
> *To:* David MacDonald
> *Cc:* 'Janina Sajka'; kirsten@can-adapt.com; public-html-a11y@w3.org
> *Subject:* Re: is role=menubar NOT for navigation menus.
>
>
>
> Hi David,
>
> I think what they are saying is that it should not be used when you have a
> site navigation region:
>
> <nav aria-labelledby="foo">
> <h1 id="foo">Site Navigation</h1>
> <a href="xxx">WAI-ARIA Home Page</a>
> <a href="zzz">Janina's accessibility corner</a>
> ...
> </nav>
>
> Really a menubar is a sequence of menu items, most of which cause a
> submenu, to be rendered.  menuitems perform an action. With these types of
> widgets you are trying to categorize and hide functions until you are ready
> to use them.
>
> I think the authoring practices should change as I agree with the person.
>
> Here is the WAI-ARIA definition of a menubar:
> http://www.w3.org/WAI/PF/aria/roles#menubar
>
> Great to hear from you! Will you be at the PF face to face in Toronto?
>
> Cheers,
> Rich
>
>
> Rich Schwerdtfeger
>
> [image: Inactive hide details for David MacDonald ---01/14/2014 04:59:13
> PM---Hmmmm... I may have answered my own question The PF best]David
> MacDonald ---01/14/2014 04:59:13 PM---Hmmmm... I may have answered my own
> question The PF best practices doc seems to talk about a links m
>
> From: David MacDonald <david100@sympatico.ca>
> To: "'Janina Sajka'" <janina@rednote.net>, <public-html-a11y@w3.org>,
> Richard Schwerdtfeger/Austin/IBM@IBMUS
> Cc: <kirsten@can-adapt.com>
> Date: 01/14/2014 04:59 PM
> Subject: is role=menubar NOT for navigation menus.
> ------------------------------
>
>
>
>
>
> Hmmmm... I may have answered my own question
>
> The PF best practices doc seems to talk about a links menu freely in this
> context. http://www.w3.org/TR/wai-aria-practices/#menu
>
> Thoughts?
>
> ========
>
> Hi Rich and Janina, et al
>
> I'm addressing a bug filed in the Using WAI-ARIA in HTML 5 document.
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=23970
>
> http://rawgithub.com/w3c/aria-in-html/master/index.html
>
> It is suggesting that menubar not be used on link navigation menus because
> the spec says it is for role=menubar should act like windows and Mac
> applications menus that have a selection of commands.
> http://www.w3.org/TR/wai-aria/roles#menubar
>
> A lot of accessible navigation menus have added that role=menubar, with
> menuitems on mega menus etc... Apparently not making a distinction between
> navigation menus application menus.
>
> I wonder if there is anybody around who was sitting in the meetings when
> they were writing up that document. If so would you say that was the
> intention of the PF at the time, to limit the menubar application type
> functionality rather than the menubar for navigation functionality? I'm
> planning on adding a section to the document that discourages using menubar
> on navigation menus. But want to ensure that that was really the intent of
> the PF team when they wrote that section.
>
> Cheers,
> David MacDonald
>
> CanAdapt Solutions Inc.
> Tel:  613.235.4902
> http://ca.linkedin.com/in/davidmacdonald100
> www.Can-Adapt.com
>
>   Adapting the web to all users
>             Including those with disabilities
>
>
>
>


image001.gif
(image/gif attachment: image001.gif)

Received on Wednesday, 15 January 2014 02:01:47 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:37 UTC