react-component / react-component/steps
Keyboard focus gets lost/ focus order is disturbed on the page affecting their understanding of the logical order of navigation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 332
- Forks
- 107
- Avg merge
- 1h 8m
- Merged PRs (30d)
- 2
Description
When invoking the next button focus gets lost and on pressing tab it goes to the first option
Example - http://react-component.github.io/steps/?path=/story/rc-steps--nextstep.
Need to enable tab index first for keyboard navigation. ^^
Contributor guide
No contributing guide indexed for this repository
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 with the rc-steps--nextstep example at http://react-component.github.io/steps/?path=/story/rc-steps--nextstep and reproduce the focus change when invoking the next button, then inspect the component entry point used by that example. Done means keyboard focus is retained and Tab proceeds through the logical navigation order instead of returning to the first option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100