musescore / musescore/MuseScore

Project Properties Keyboard Navigation getting stuck in Copyright Field again

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

@shoogle is already working on this.

Since Jun 12, 2026.

accessibility needs review regression MS4
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

This was an issue previously (See #19134) which was fixed in 4.2 but is now back in 4.7.

STEPS:

  1. Open project properties.
  2. Arrow down the fields, Work Title, Composer, etc till you get to copyright.
  3. Try arrowing further and you will see navigation is stuck.
  4. Pressing Tab will take the user to the OK button and they may be unaware there were more possible fields, or unable to find a way back to them with keyboard navigation.
Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.7.2

Regression

Yes, this used to work in a previous version of MuseScore 4.x

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.