musescore / musescore/MuseScore

No ability for Screen Reader to report current Page/System

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

@shoogle is already working on this.

Since Jun 26, 2026.

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

In most software screen reader users have a shortcut key to read the status bar and often this reports the page/line count as well as other info. In NVDA this is NVDA + End, i.e. Insert + End. As the MuseScore status is for the most part being read by the screen reader with each movement and possibly doesn't contain this info anyway could we use this shortcut to instead report the current page and system.

Currently there is no way for a blind user to know the page layout and system layout is also very hard to determine. This makes it hard to layout something for print readers or to know where you are when communicating with people using the print score. This is an issue which seems to be causing a lot of difficulties.

Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.7.3

Regression

No.

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.