musescore / musescore/MuseScore
Left/Right Arrows navigate incorrectly between bars in the Braille Panel
Open
@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
When on the last element /Braille cell of a bar in the Braille panel pressing a right arrow does not advance to the first element/cell of the next bar. Only the Ctrl + arrows to move along or back bar by bar seem to work.
STEPS:
- Open any score with more than 1 bar of notes.
- With focus on the first note of the score and in Normal mode press tab to move to the Braille panel.
- Press right arrow to move along the notes of the bar. Notice they sound and the Braille cursor advances as well as focus on the score moves note by note.
- At the end of the bar press right arrow again. Notice there is no further advancement. The navigation is stuck.
- Press Shift Tab to move back to the score.
- Press right arrow and see how it now advances to the next bar. This should be the same in the Braille window.
Ideally where ever possible the navigation in the Braille panel with keyboard shortcuts should mirror score navigation.
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
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.