musescore / musescore/MuseScore

Focus does not stay on the Braille window when Ctrl F is initiated from Braille panel

Open
#29,411 0 comments 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

Since Aug 22, 2025.

accessibility braille nav 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
  1. Open a score and press tab to move focus to the Braille window.
  2. Press Ctrl F and type a bar number followed by enter.
  3. Notice the focus moves to the bar specified, but on the score not Braille window, and Braille shows what the screen reader has just said rather than displaying the bar (this is usual when focus is on the score). If initiated from the Braille Window then focus should move to that bar on the Braille and Braille refresh to show it. The score should scroll as needed to keep it in view and highlight the same item where Braille is focused.
    Focus should also be on the same staff as the command was initiated from (see #29410
Supporting files, videos and screenshots

N/A

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

4.5

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.