musescore / musescore/MuseScore
Braille and Score Navigation do not sync to each element
Open
@shoogle is already working on this.
Since May 29, 2026.
accessibility
braille nav
- 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 navigate to an articulation, fingering and various other elements on Braille focus moves to the corresponding note on the score rather than the element itself. If you Alt arrow on to an element (other than note or rest) on the score the focus on the Braille panel is a bit random.
STEPS:
- Add a few notes with a variety of dynamics, articulation, fingering, ornaments, other elements and lyrics.
- Use Alt arrow to move along each element and notice that on the Braille panel the cursor does not always move to the exact corresponding Braille sign for that element. Lyrics, Dynamics and notes seem to work well.
- Move with Alt arrow to a lyric and notice the Braille moves to the lyric line and seems to have the cursor on the correct word in the Braille line.
- Move to the next element after a lyric (any element not a note or rest) and Braille will often stay focused on the lyric line.
- Tab to the Braille panel and arrow along. Notice that focus on the score moves correctly to the corresponding note and dynamic generally, but if you move to an articulation, fingering and various other symbols focus on the score moves to the note it is attached to rather than the element itself.
This needs fixing before issues with editing in the Braille panel can be fixed.
Supporting files, videos and screenshots
N/A
In which versions of MuseScore Studio is this issue present?
4.7
Regression
No.
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.