phetsims / phetsims/wave-interference
Suggestion for keyboard nav order
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Test device
Lovelace
Operating System
ChromeOS
Browser
Chrome
Problem description
For https://github.com/phetsims/QA/issues/511
If using keyboard nav, you pass through a number of options on the panel when going between the on/off for the wave source and the continuous/pulse options. This makes sense in regards to where everything is on the screen. However, since switching turns off the current wave, and after a switch between continuous and pulse the first thing a user is likely to want is to turn on the source, I'm wondering if they should be closer in the nav order. Minor issue.
Visuals
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 by reviewing QA issue 511 and reproducing the keyboard navigation behavior in Chrome on ChromeOS. Compare the current order of the wave source on/off control and continuous/pulse options; done means the navigation order reflects the suggested workflow without disrupting the panel layout or other controls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100