musescore / musescore/MuseScore

Various items do not scale for Low Vision Users

Open
#31,763 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accessibility
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
  • Colour picker: this sub menu (accessed whenever the user tries to alter the colour of an element) has tiny icons and the text size doesn’t scale up to match the user’s preferred text size.

  • Tooltips/icon label text is not scalable. In iOS this can be solved using Hovertext, which will produce a label in the user’s preferred size, but it is slow to respond and there is no equivalent accessibility feature in Windows.

  • Icon size: the graphic icons within the palette submenus currently remain the same size, regardless of the font size selected, whilst the icons in the note editor toolbar scale up. The time and key signatures are especially hard to read. This is somewhat solvable in iOS if the user has Hovertext enabled but see the previous note re response time and operating system.

  • Mixer palette: It’s hard to set the levels as the sliders and numbers are very small. These either need to be made bigger, or an alternative method is needed.

  • The scroll bars throughout the software are tiny and hard to find.

Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.5.2

Regression

I was unable to check

Operating system

iOS: Sequoia 15.6

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.

Research direction

Start by reproducing the low-vision problems described in MuseScore Studio 4.5.2, checking the colour picker, tooltips, palette icons, mixer palette, and scroll bars. No source files, tests, or entry points are named, so the first task is locating each affected UI component. Done means the affected controls and labels scale appropriately or provide a usable alternative.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
accessibility, desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.