musescore / musescore/MuseScore
Request a shortcut key to open shortcuts list using a screen reader
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Your idea
The shortcuts list can be very useful for those using screen readers. Unfortunately it takes many keystrokes for the screen reader user to get to the shortcuts item in Preferences. so my suggestion is to have a shortcut to quickly open up the shortcuts dialog.
Currently to open this dialog one must hit alt+V (to get to the View menu), arrow up to Preferences, hit enter to open Preferences.
Then, instead of focus being on the list of topics (as it should be), focus is on the language setting and one has to tab several times to get to the list of topics. Then, finally, one can arrow down to the Shortcuts topic. A lot of keystroeks to find a hotkey for doing something using the keyboard (which is how screen reader users interact with their PC's!).
also, I noticed that when searching for a shortcut, one has to tab twice, passing over some button about "sorting order", before getting to the list of search results. Would be more efficient if the search results just showed up as a list in the edit field itself, or if the search results were placed immediatly after the tab stop for the search edit field.
--Pete
Problem to be solved
Efficiency of navigation for screen reader users
Prior art
No response
Additional context
No response
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 in the View menu and Preferences flow, then inspect the shortcuts dialog and its search-results focus order. The change is complete when screen reader users can open the shortcuts list directly with a shortcut and can reach search results without unnecessary tab stops.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- accessibility, desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100