musescore / musescore/MuseScore

Screen Reader does not differentiate type of tempo changes

Open
#27,952 0 comments 1 reaction 1 assignee View on GitHub

@shoogle is already working on this.

Since May 6, 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

When arrowing over notes the screen reader announces rit. rall, accel, a tempo etc all as "start of gradual tempo change" and "end of gradual tempo change".

STEPS:

  1. Make a range selection of a bar of a score.
  2. Select rit from the tempo palette.
  3. Use arrow keys to navigate across the first to last notes of where the rit was just entered.
  4. Note that the screen reader announces "start of gradual tempo change" on the first note and "end of gradual tempo change" on the last note.
  5. Repeat the above, but insert a different mark such as accel.
  6. Note: The speech output is identical making it impossible to know what type of tempo change is on the score.
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

Additional context

Tested with NVDA screen reader

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.