W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2012

Re: Officially suggested keyboard interaction for sub-menu items in the "navigation"?

From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Date: Mon, 30 Jul 2012 07:57:44 +0100
Message-ID: <CAEhSh3cMJ5=yW61togwCycjLFbzmf7KGOYeDO-3FtQR-33xnKA@mail.gmail.com>
To: Ian Yang <ian@invigoreight.com>
Cc: w3c-wai-ig@w3.org
On Mon, Jul 30, 2012 at 2:00 AM, Ian Yang <ian@invigoreight.com> wrote:
> Do we have a conclusion? Taking a look on the previous code again, and there
> is a dilemma: when the focus is on the "About" menu item, should hitting
> Enter key toggle the sub-menu or take users to about.html? There is no
> specification addresses this issue. So it seems to be wrong to put a
> "menubar" in the "navigation"?

Yes. The problem is navigation lists have different user expectations
from application menu bars, precisely because the top-level items
often have a primary purpose of acting as links!

I think there are are two good approaches here that don't violate user

1. If the top-level items take the user to hub pages from which their
child items are themselves accessible as links, don't try to make the
child items keyboard navigable (leave their container display: none or
remove it from the DOM). They can be quick-access lists on hover for
mouse users. Keyboard users access the subitems through the hub pages
(or site search, or a sitemap, or an external search engine).

2. If there's an icon indicating a top-level item has a child list
such as a downwards pointing arrow, you can turn that into a separate
button for opening the sublist as a popup with alternative text like
"Open about sub-links". You may wish to markup the list opening button
with @aria-haspopup and mark the opened list up as a dialog:




Benjamin Hawkes-Lewis
Received on Monday, 30 July 2012 06:58:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:40 UTC