musescore / musescore/MuseScore

Accidentals on Ornaments not read by Screen Reader or Braille

Open
#27,670 1 comment 1 reaction 1 assignee View on GitHub

@shoogle is already working on this.

Since Apr 14, 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

If an ornament such as a trill, turn, mordent, etc has an accidental above or below these are not read out by the screen reader or displayed on the Braille panel.

STEPS:

  1. Add an ornament such as a turn to a note.
  2. Go to Properties and change the interval above for this ornament to something not diatonic so an accidental appears above the turn.
  3. Tab to the score and use Alt with left and right arrows to move from the note to the ornament.
  4. Notice the screen reader announces the turn but does not speak that it has an accidental.
  5. Tab to the Braille panel and if you compare the output with and without the change of accidental you will see it has not added dots before the turn (A turn is represented by dots 6, 256 before the note it is above and if it has an accidental above it this sign will appear in front of the turn, so a turn with a sharp above will be sharp sign 146, followed by the turn 6,256.). The accidental on the ornament is not shown.
Supporting files, videos and screenshots

N/A

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

4.5.1

Regression

Choose option...

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.