musescore / musescore/MuseScore

Unable to Navigate in Braille Panel in Note Input Mode

Open
#27,833 3 comments 1 reaction 1 assignee View on GitHub

@shoogle is already working on this.

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

In Note Input you can enter notes, but you can't navigate
• In Normal mode, you can navigate but can't enter notes.
Ideally, it should behave the same as the main score window: navigation should be allowed in whatever mode, entering a note or rest should switch to Note Input.

STEPS:

  1. On a score with some notes press N to ensure you are in Normal mode.
  2. Press Tab to move to the Braille panel.
  3. Press left & right arrows, the cursor moves as expected and the notes play as you arrow along the Braille.
  4. Note that the focus has moved back to the corresponding note in the score as you move along the Braille.
  5. Press N to move to note input mode.
  6. Press left/right arrows to move along the Braille.
  7. Notice this time the notes do not sound, Braille dot numbers are read and the focus on the score does not move. In effect the Braille cursor looks as if it is moving but there is no effect.
Supporting files, videos and screenshots

N/A

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

4.5.1

Regression

No.

Operating system

Windows 11

Additional context

using NVDA screen reader

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.