-
Notifications
You must be signed in to change notification settings - Fork 377
fix(Menu/Nav): flyout variants work with VO navigation #7772
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Preview: https://patternfly-react-pr-7772.surge.sh A11y report: https://patternfly-react-pr-7772-a11y.surge.sh |
Yeah the Nav flyout example I don't think makes it entirely clear how to navigate/operate things. It also doesn't help that with VO active (and I believe NVDA is the same as well), the Left/Right Arrow keys on their own navigate through the content of the page, so I don't believe we'd be able to rely on pressing those keys to open/close flyout menus. I should have included that in the original issue content, as what I wrote does make it sound like pressing Right Arrow with VO active would open the flyout. I'm able to get the Nav flyout to open by pressing only |
wise-king-sullyman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that in Firefox the nav flyout is missing the "menu pop up" announcement doesn't work with VO, which leaves the a11y for it about how it was before this change.
The composable flyout does seem substantially improved though! Awesome work on that! If you would want to open a followup issue for the nav portion of this I'd be happy to approve this now 🙂
wise-king-sullyman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
|
Your changes have been released in:
Thanks for your contribution! 🎉 |

What: Closes #7461
Composable flyout menu demo
Nav flyout example
VO modifier + spaceregisters as a click event, I added a check for a "click" mouse event for thehandleFlyoutmethod.aria-expandedandaria-haspopupprops to the Nav Item, following the logic from Menu Item. This will at least provide context that the nav item a) has a popup menu, and b) is expanded/collapsed, and you can choose between clicking the link with VO + space, or opening the flyout with just space. I believe this is about as close as we can get to resolving the flyout issue for the Nav component unless one of the following is done:<a>element to make it a sibling instead, and make it an actual button that can be used to click on and open the flyout. Similar to the W3C flyout button as toggle example (this would require an update in Core).Additional issues:
N/A