musescore / musescore/MuseScore

Edit Panels of pasted items do not read with Screen Reader

Open
#29,741 2 comments 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

Since Sep 9, 2025.

accessibility needs review
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
  1. Add some staff text to a note.
  2. Use Alt arrows to move off the edit panel and back on to it.
  3. Press Ctrl C to Copy the Staff text.
  4. Move to a new note and Press Ctrl V to Paste it.
  5. Use Alt arrows to move across both notes and their associated staff text edit panel. Notice that the original one announces when you Alt arrow on to it "staff text" and reads the staff text whereas the one that has been pasted does read correctly when you are on the associated note but when you Alt arrow right on to the edit area there is no feedback at all from the screen reader.

The same result is observed if you copy/paste pedal marks, ie as you arrow over the notes the screen reader announces, start/end of pedal as expected. But, when you alt arrow on to the edit panel itself there is no feedback on the pasted one.

i have not tested if this effects other items also.

Supporting files, videos and screenshots

N/A

What is the latest version of MuseScore Studio where this issue is present?

4.5

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.