-
Notifications
You must be signed in to change notification settings - Fork 830
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
[EuiButtonGroup] Keyboard navigation through items #8033
Comments
I'm not convinced the component is a toolbar - that feels a touch too prescriptive for what's essentially a styled |
I'm not saying the header is a toolbar, I'm saying the items in an So, in this Kibana header, these three buttons on the right, together, act as a toolbar: The idea of header sections makes sense, but I was a bit surprised that there were In most uses of the header there's a group of buttons on the right, and those are the ones that have a toolbar role. |
I guess the thing I struggle with is that I don't see If we want to create a new semantic component called |
@alexwizp Any chance you could weigh in on this as well? 🙏 I'd super appreciate your a11y expertise! |
@cee-chen yes in this specific case it's arguable whether those are a "toobar" or just buttons next to each other. If you don't mind I'll update the issue to be specific to In these cases it's clear that this is a composite component and all the buttons "belong" together in the group and you should be able to use left/right/home/end to move through them. |
@smith We actually just went through this discussion fairly recently with EuiButtonGroup and moved away from this UX because it's misleading. Several of our accessibility engineers/contractors/the internet agreed: |
My 2c: what constitutes a "toolbar" is content/context dependent and not something EUI can simply wholesale apply to presentational or functional components. We need consumers to make this determination themselves. My suggestion for toolbar/tab stop behavior would be an accessibility or utility helper, e.g.: <EuiTabStop role="toolbar">
<EuiButtonGroup options={...} />
</EuiTabStop> |
I don't know if having behavior like radio buttons is the intention of the toolbar pattern. I don't feel all that satisfied about what, if any, conflict there is with the APG so I might ask around about some details. I'll close this. Thanks for your input. How about tabs? If I have one tab focused I would expect left/right would move the focus between tabs (radio button style, I guess.) That's not how EUI works. Should it? |
Describe the problem
When using keyboard navigation and tabbing in to an EuiButtonGroup, you should be able to use the arrow keys to navigate between the items
This component should behave according to the Toolbar pattern in the ARIA Authoring Practices Guide
To Reproduce
Proposed solution
Implement keyboard behavior that allows you to use the arrow keys within the list.
WCAG or Vendor Guidance (optional)
The text was updated successfully, but these errors were encountered: