musescore / musescore/MuseScore
Improve screen reader readout of 'Voice assignment' buttons in properties
Open
@shoogle is already working on this.
Since Mar 11, 2026.
accessibility
P2
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Follow up from https://github.com/musescore/MuseScore/pull/31853#issuecomment-3785572441 (pasted below)
Problem
Generally, when a radio button option that's part of a properties control is focused on by the screen reader, what's read is the property name followed by the button name, like this:
Position Above, radio button
...but for the 'Voice assignment' buttons, the property name is not read before the button names:
Task
Make the screenreader read out the following for each button:
All:
- For multi-staff instruments, when the 'parent' button is hovered, ideally it would read the name of whichever of the two options is currently selected:
- Voice assignment, All voices on instrument, button
- Voice assignment, All voices on this staff only, button
- For single-staff instruments, it should just read:
- Voice assignment, All voices on instrument, radio button
- if we can't make it say 'radio button' (as opposed to 'button' as it says now), that's okay for now.
- Voice assignment, All voices on instrument, radio button
Individual voices:
- Voice assignment, Voice 1, radio button
- ...
- Voice assignment, Voice 4, radio button
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.