Open dozer75 opened 6 years ago
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.
Find more details about Angular's feature request process in our documentation.
Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.
We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.
You can find more details about the feature request process in our documentation.
Feature request
What is the expected behavior?
In HTML 5 it is possible to add the accesskey attribute to any element, in HTML 4.01 it's possible to set this on anchors, areas, buttons, inputs, labels, legends and textareas.
Any material component that uses one of these should support setting accesskey and pass it to the main html element beneath like other element attributes.
What is the current behavior?
As far that I can see no material components are implementing accesskey.
What is the use-case or motivation for changing an existing behavior?
We are trying to give users the ability to use keyboard instead of mouse or other pointing tools to be able to use our Angular application. This would help that.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 6.0.3 Material 6.2