You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not convinced the component is a toolbar - that feels a touch too prescriptive for what's essentially a styled <header> element. Should all semantic headers have arrow key/tabstop behavior?
I'm not convinced the component is a toolbar - that feels a touch too prescriptive for what's essentially a styled
element. Should all semantic headers have arrow key/tabstop behavior?
I'm not saying the header is a toolbar, I'm saying the items in an EuiHeaderSection make up a toolbar.
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 EuiHeaderSectionItems and EuiHeaderSectionItemButtons. I would have expected there to be a section that I put a button group in.
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.
Describe the problem
When using keyboard navigation and tabbing in to an EuiHeaderSection, 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: