musescore / musescore/MuseScore
Incomplete Speech Output for Metronome toggle with 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
Issue type
Accessibility issue (e.g. for keyboard-only or screen reader users)
Description with steps to reproduce
- With NVDA screen reader enabled open a score and press Ctrl M a few times to toggle the metronome on and off.
Notice that each time you do this the screen reader just announces "Metronome" but does not say whether the metronome has been toggled on or off. Ideally this would say "Metronome On" and "Metronome Off".
In 4.5 this key press did not result in any speech. Speech should announce a change of state or an action that has happened rather than simply echo a key press function.
Supporting files, videos and screenshots
N/A
In which versions of MuseScore Studio is this issue present?
4.6.1
Regression
I was unable to check
Operating system
Windows 11 with NVDA
Additional context
No response
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
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
Reproduce the issue in MuseScore with NVDA by opening a score and pressing Ctrl+M to toggle the metronome. Trace the metronome toggle's accessibility or speech announcement path; done means NVDA announces whether the metronome is on or off after each toggle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- accessibility, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100