Add support for accesskey
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 25k
- Forks
- 6.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 91
Description
#### 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating how Angular Material components forward standard element attributes, then inventory the components whose underlying elements can support accesskey; done means the attribute is accepted and passed through consistently, with coverage for the affected components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- accessibility, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100