musescore / musescore/MuseScore

Colour Descriptions in the Apperance Preferences not meaningful to screen readers

Open
#20,182 0 comments 0 reactions 1 assignee View on GitHub

@Eism is already working on this.

Since Nov 25, 2023.

accessibility needs design needs info P2 UI
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UI bug (incorrect info or interface appearance)

Bug description

In the Appearance tab of Preferences, the speech gives RGB descriptions of colours. This is much less meaningful than descriptive names for each colour. Descriptive names could be calculated (if customisable) or given predetermined names (if there are only a limited number of predetermined colours only).

Steps to reproduce
  1. From the Edit menu, choose Preferences.
    The Preferences dialog appears.
  2. Choose Appearance from the list of tabs.
    The appearance preferences appear.
  3. Move through the list of available colour choices.

Expected output: Meaningful colour names, such as "white", "cream", "tan", "yellow", and so on.

Actual behaviour: Red/green/blue (RGB) percentages are announced, such as "Red 94 percent Green 52 percent Blue 52 percent".
Such RGB descriptions may be technically accurate, but are of little practical value, leading to confusion. They are also very verbose. The above example would be better announced as "red" or "bright red".
Colour descriptions can be predetermined, if the colours cannot be changed, or can be calculated based on converting RGB to HLS model and creating a description.

Screenshots/Screen recordings

No response

MuseScore Version

4.1

Regression

I don't know

Operating system

Windows 10 with NVDA

Additional context

No response

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.