musescore / musescore/MuseScore

Keyboard navigation between staves broken on Multi-Bar rests

Open
#33,789 0 comments 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

Since Jun 12, 2026.

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

If the user uses keyboard navigation to move on to a multi-bar rest they can then not use Alt + Up or Down arrows to move to other staves. This is especially confusing if the score begins with a multi-bar rest and the user then doesn't realise there is more than 1 staff present.

STEPS:

  1. Open the attached score (or create one with at least 2 instruments and beginning with a multi-bar rest).
  2. Press Right then left arrow to hear the multi-bar rest read.
  3. Now Press Alt + Down arrow to attempt to move down onto the second staff (oboe on the attached score). The screen reader says "Down note in chord" and the user will assume there is only 1 staff.

multi-bar rests.zip

Supporting files, videos and screenshots

As above

In which versions of MuseScore Studio is this issue present?

4.7.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.