musescore / musescore/MuseScore
Screen reader issues with dynamic popup
@shoogle is already working on this.
Since Mar 27, 2026.
- 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
When arrowing through the dynamic pop up the screen reader speaks the title "Dynamic Pop Up Panel" before a number of items (possibly top of columns or grid, etc). The problem is that this sounds like a heading and the user will quickly press the arrow again to move on, but it is actually one of the dynamic options prefixed with this additional speech. one of these is the "Other Dynamic Button" which reads as "Dynamic Pop Up Panel other Dynamic Button". As well as being very verbose the user will have moved on and not know this button is present.
STEPS:
- Navigate to a dynamic using Alt right arrow, then press tab to move on to the dynamic Pop Up.
- Press any arrow key multiple times to navigate through the full list of items. Notice the additional speech on some items.
- Now navigate quickly with arrows as if skimming through the list and notice you end up skipping the items with the additional speech.
Supporting files, videos and screenshots
N/A
In which versions of MuseScore Studio is this issue present?
4.6 (4.7 beta)
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.