musescore / musescore/MuseScore

RNA (Roman Numerals) not reading on notes with screen reader

Open
#31,447 2 comments 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

Since Dec 16, 2025.

accessibility needs review regression MS4
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 you arrow along notes that have Roman Numerals attached the screen reader no longer announces the value of the Roman Numeral, it just says Roman Numeral.
When you alt arrow on to the Roman Numeral itself the speech is now very verbose.
This was working correctly a few months ago so has changed somewhere in the 4.6 updates.

STEPS:

  1. Write a few notes and add a Roman numeral to each.
  2. With screen reader on arrow along the notes and note that after it announces the note/bar/beat, etc it just says "Roman Numeral" it used to announce what the Roman numeral is e.g. Roman Numeral four, roman numeral two b, etc.
  3. Now Use alt arrow to move on to the Roman Numeral itself and instead of hearing Roman numeral four" or "Roman numeral iib",etc you get "Roman Numeral bar 2 beat 1 Edit two back slash b".

This is incredibly difficult to use when working with choral harmony as arrowing along the Bass line no longer announces the Roman Numerals at all and the output when you do alt arrow on to them can be difficult to navigate amongst multiple voices on a staff as well as giving incredibly verbose output that does not actually speak the name of the chord as expected and is hard to hear for example V or b in a string of words when it should have announced Five for V. This is making this kind of work almost impossible while trying to get this info and memorise all the parts above!

Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.6.4

Regression

Yes, this used to work in a previous version of MuseScore 4.x

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.