Entering the table requires an additional tab stop, because the entire table is selected before going through the table elements.
Open
Nobody has claimed this yet.
discussion
- Dominant language
- TypeScript
- Stars
- 80
- Forks
- 22
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 118
Description
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
Start by reproducing the issue in the table component with keyboard Tab navigation, then locate the table implementation and any existing keyboard-navigation tests. Confirm the current extra selection stop and define done as entering the table and reaching its elements without requiring an additional Tab stop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100