musescore / musescore/MuseScore

Dynamic Popup opening with Tab breaks navigation to Braille Panel

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

@shoogle is already working on this.

Since Aug 19, 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
  1. Ensure the Brailll window is enabled.
  2. Navigate to any note on a score and press tab, notice focus shifts to the Braille window.
  3. Navigate to a dynamic n the score and press Tab, notice the Dynamic Popup is opened.

This breaks navigation to the Braille panel when on a dynamic mark. Tab should always jump to the next panel top level item.

However, I'm not sure if this is the way this was designed for all users to open the dynamic popup with Tab as pressing Enter or F2 seems to get a different result for me.

  1. With screen reader enabled navigate to a dynamic mark and press Tab. Notice you can then arrow down through the dynamic options of ppppp to fffff, and then down to fp, sfz etc. However, I couldn't get to cresc or hairpins if they are there and left/right arrows seemed very confusing to navigate. .
    2Navigate to the place that says "other Dynamic Button" and pres enter, nothing seems to happen. No more options seem to appear.
  2. Press Esc to close and again navigate to a dynamic mark and this time press F2 or Enter. Some sort of window opens but the screen reader is completely silent with all arrows, tabs or other movement, so unsure if this is the same window or something different?
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.