E-mail List Archives

Keyboard Navigation Pattern for Navigation Menu with Submenu

for

From: Snahendu Bhattacharya
Date: Jun 24, 2016 2:16PM


Hi All!

I have one question regarding the keyboard navigation pattern for
navigation menu with submenu.

As per WCAG 2.1.1, it all functionality should be available through a
keyboard interface.

Necessarily it doesn't talks about the pattern on the keyboard navigation
order as that is more a usability issue rather than Accessibility.

*Current keyboard navigational pattern of the menu:*

>> As soon as user TABs to the menu, Submenu opens automatically.
>> If user tabs, focus goes to the next menu (not the submenu)
>> If user uses UP/DOWN arrow key they can navigate to the submenus.

Technically this is accessible as the functionality is accessible through
keyboard.

*Note:* For screen reader user appropriate roles, States, properties and
instructions are provided.

*Question is:*
Does this provide right user experience?
Does all the submenu need to be made available through TAB key?
(Considering the fact auto open functionality of the menu can't be changed)

*For the second question* my personal view is, if user is forced to
traverse through all the menus while pressing TAB (even if they don't want
to see those), would cause more usability issues.

*Can you please let me know your thoughts?*