musescore / musescore/MuseScore

Start & End of Hairpin & Pedal mark Lines do not read with screen reader if adjusted off a note.

Open
#28,037 0 comments 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

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

STEPS:

  1. Write 4 quarter notes in a bar.
  2. Select these and add a crescendo hairpin from the Add menu.
  3. Use arrows to move over the first and last note of the bar and hear that it correctly announces start of hair pin crescendo on the first note and end of hairpin crescendo on the last note.
  4. Use Alt arrows to move to the hairpin panel after beat 1.
    Hold down shift and press right arrow once to extend the hairpin.
  5. Now arrow again over the notes, and notice it does not say end of hairpin crescendo anywhere, a blind user does not know where this ends or how long it is.

Repeat the above steps with a pedal mark and note the screen reader can no longer read the end. The same applies to the start if it is shifted. So, a pedal mark or hairpin that has had both ends adjusted to a mid note point can completely disappear to a screen reader user.

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

Using 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.