-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Bug: md-toolbar should have role of toolbar #2909
Comments
* Add the toolbar `role` attribute to the host element to have proper accessibility support. Fixes angular#2909
@bsteffl Thanks for the great issue reports! Regarding keyboard interaction, I don't think that the toolbar should be responsible for such things. The toolbar is meant to be very simple and should just follow the design guidelines. |
* Add the toolbar `role` attribute to the host element to have proper accessibility support. Fixes angular#2909
* Add the toolbar `role` attribute to the host element to have proper accessibility support. Fixes angular#2909
@devversion I appreciate your support for accessibility and being inclusive. Keyboard users will still have access to buttons via tabbing so not supporting keyboard actions works too. When I included that I was just thinking about how native OS toolbars work and users understanding of those. Thank you for your contributions. |
* Add the toolbar `role` attribute to the host element to have proper accessibility support. Fixes #2909
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug:
Md-toolbar should have
role="toolbar"
What is the expected behavior?
WCAG Guidelines
What is the current behavior?
No toolbar role is announced. Would be nice to also provide keyboard functionality for
Left Arrow
andRight Arrow
.What are the steps to reproduce?
What is the use-case or motivation for changing an existing behavior?
Meet accessibility requirements
Which versions of Angular, Material, OS, browsers are affected?
2.0.0-beta.1
The text was updated successfully, but these errors were encountered: