musescore / musescore/MuseScore

Arrowing falls off list-like controls into other controls

Open
#28,515 1 comment 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

When the focus is on a list type control, such as the categories in the New Score wizard, continuing to arrow beyond the first/last item in the list focuses a different control. This could result in confusion.

Steps:

  1. From the File menu select New or press Ctrl+N.
    The New Score wizard appears.
  2. Select the Choose instruments radio button.
  3. Tab to the categories.
    Focus is on Woodwinds.
  4. Arrow Down to move through the available categories.

Expected behaviour: Each category should receive focus and be selected. Movement should stop at the last category, e.g. Strings - Bowed.

Actual behaviour: Focus falls out of the list and continues to "Common combo box", and then re-enters the category list. Also, nothing is selected by arrows.

Supporting files, videos and screenshots

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