musescore / musescore/MuseScore

Some Users Unable to Change Staff in Note Input Mode in Braille Panel

Open
#28,496 0 comments 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

Since Jun 20, 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

(For some users?) In Note Input mode in the Braille Panel, if you press Arrow Up/Down to show a different staff, additional notes still end up on the original staff.
The user has to go back to the main score to shift staves and then return to the Braille panel to enter on another staff.

STEPS:

  1. Set up a blank score with at least 2 staves and focus on an empty bar of top staff. Press N for Note Input.
  2. Tab on to the Braille panel. Input some notes e.g. Middle C semibreve by pressing k, fsjkl. The note sounds and dots 5, 13456 are displayed (for some a left or right arrow needs to be pressed to make them display)
  3. Press down arrow. The display will now show the whole bar rest (dots 134) of the stave below.
  4. Attempt to enter a C3 semibreve (jkl, fsjkl).
  5. The note should sound and be entered on the score and display on Braille panel and Braille display.
  6. Actual results vary, this works for some, but for others the note is entered on the next bar of the first staff.

At this point quite a number of users have reported this same behaviour but we have not found what is common to those users and not to others who have it working fine. Except that users who do not see this behaviour do tend to be more likely to not have notes appearing as they are entered in real time #23176.

Supporting files, videos and screenshots

N/A

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

4.5.2

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.