musescore / musescore/MuseScore
Selection filter voice and chord buttons don’t report state to Screen Reader
Open
@shoogle is already working on this.
Since Jun 23, 2026.
accessibility
P2
- 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
STEPS:
- Open a score with notes in at least 2 different voices.
- Navigate to the selection filter.
- With screen reader enabled use arrow keys to move through the list of voice buttons and hear each announce "voice 1 button", "voice 2 button", etc.
- Press enter on any voice.
- Arrow again across the voice buttons and hear that nothing has changed, none of them report their status as selected or not selected and there was no feedback from the screen reader when enter was pressed on one to say what happened, if anything.
- Using a score with some chords select all of one staff (including chords).
- Navigate back to the selection filter and arrow through the options for chords. You hear "Top note button", "bottom note button" etc but they do not announce state.
- Press enter on one of these and again the screen reader gives no indication of what has been selected/filtereds.
It is very hard for a blind user to make any use of this when you don't have feedback to know what you have or have not selected.
Supporting files, videos and screenshots
N/A
In which versions of MuseScore Studio is this issue present?
4.7.3
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.
Assessment
This issue has not been assessed yet.