> > > Sorry to say this but the keyboard friendly version: > > http://tjkdesign.com/articles/keyboard_friendly_dropdown_menu/EK.asp > > > > Only fires, via keyboard, on "Articles E-K" in IEv8 or Firefox. > > This is by design. Keyboard users could not reach these pages if they were > not focusable at least from the parent page. > > The "About this solution" section says: > > "Note that keyboard users cannot skip the sub-menu related to the current > page. This is because this sub-menu is exposed to SE (Search Engines) and > thus accessible to keyboard users when JS is off." > > The sub-menus open via the *enter key*, this is to allow keyboard users to > skip sub menus so they are not forced to tab through all the menu items. > If the menu is "accessible", it is *because* the sub menu related to the > page itself *is* focusable (it is not styled with display:none). > > > What this menu is missing though is a arrow pointer for *discoverability*. > I > have a title in there, but I think it's pretty useless (for 99.99% of > users). If I had time, I'd add arrows and ARIA roles too. >
I have a bug report... tested against FF 3.6.4 and IE6 (no bug under Chrome 5.0.376) Steps to reproduce: - click on background - tab to focus first menu item - hit enter to display sub-items - tab through to the second menu - hit enter to display its sub-items (the first menu closes) - hit shift-tab to go back to the first menu The bug is either one of a) the first menu shouldn't open as the second menu is active, or b) that the second menu stays open. regards, Mathew Robertson ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
