make shortcut button and submenu accessible (#7833 reopened)

[robfentress]

Issue #7833 is still a bug (it is not really a feature request, since it presents a real barrier for some people). See the Web Content Accessibility Guidelines Success Criteria 2.1.1 Keyboard for details on why the current implementation is problematic, if you are unsure. I would like to be able to recommend the use of Storybook to others in our organization, because it is awesome, but cannot, because we have made a commitment to equal access for people with disabilities.

A good example of one way to handle the main menu functionality can be found in the Cauldron Library's Menu Navigation Composite Widget. For an example of a good way to handle the shortcut button, see Cauldron's Option Menus Component.

[shilman]

@robfentress Any interest in giving this a shot? PR's very welcome!

[robfentress]

Oh no, I was afraid you were gonna say that! :-)

I'd love to, but, realistically, I don't see it happening anytime soon. When I get a free minute, I'll look at the code to see how hard it would be.

[robfentress]

Hey, @mikesir87. Any interest in taking this on?

[stale]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[stale]

Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook!