musescore / musescore/MuseScore
Excess Speech Output on Play 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
In 4.6when you press space bar to Play or to pause the screen reader announces "Play". Speech is generally unnecessary and creates more chatter if the resulting action is clear without any announcement. e.g. the music starts playing or stops playing. But in this case the announcement of the word "Play" can be distracting or even make it hard to hear the first note of the section being played. Can this be silenced again as it was in 4.5?
Supporting files, videos and screenshots
N/A
In which versions of MuseScore Studio is this issue present?
4.6.1
Regression
Yes, this used to work in a previous version of MuseScore 4.x
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 Studio 4.6.1 on Windows 11 with NVDA by using the space bar to play and pause, then compare the behavior with version 4.5. The fix is complete when playback still toggles correctly without the redundant “Play” announcement that obscures the first note.
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
- 45/100