musescore / musescore/MuseScore

Cannot Select Colours in Appearance Preferences

Open
#28,500 0 comments 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

If the button to access custom colours is pressed, navigation goes wrong and a second MuseScore window can appear.

Steps:

  1. From the Edit menu select Preferences.
  2. Select the Appearance tab.
  3. Tab to the Background Colour radio button.
  4. Arrow Right to the button showing the current colour
    Actual output could be e.g. "Red 0 percent Green 0 percent Blue 0 percent button"
  5. Press Space to activate the button.
    Actual output: Speech says Basic Colors Alt+B
  6. Press Space to activate the button.
    Actual behaviour: nothing happens.
  7. Arrow Up/Down
    Actual behaviour: nothing happens.
  8. Arrow Left/Right or press Tab:
    Actual behaviour: focus returns to MuseScore, but the Color dialog is still there as well.
Supporting files, videos and screenshots

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