musescore / musescore/MuseScore

Insufficient Speech entering finger numbers, lyrics, chords, etc

Open
#34,538 0 comments 1 reaction 1 assignee View on GitHub

@shoogle is already working on this.

Since Aug 11, 2026.

accessibility
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

Currently when you are entering Lyrics, Finger Numbers, Chords, Roman Numerals (and possibly other items) when you advance to a new note you hear
"Finger Number bar X, Beat X, edit blank".

This means for a blind user you have to try and memorise the notes of your score and imagine print or Braille as you move to know what note you are adding these to. This means most users could only enter a couple at a time without having to come out of that mode and check their position, memorise the next few notes and resume.

Instead it should speak the pitch name and other details as usual when you navigate through a score. Some mid note positions for Chords would best still just speak the bar and beat as it does currently.

It would also be helpful if the notes could play as usual when navigated on to.

Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.7.4

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.