musescore / musescore/MuseScore

Correct speech output stops when making a range selection over lines or slurs

Open
#30,465 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

When making a range selection if you try to select over a slur, hairpin, pedal marks (probably more) you start to hear “add next chord to selection” with each press and stop hearing the beats, sometimes if it comes across the end of the line (slur, pedal, etc) it kicks in again with the full announcement of the range selection, but not sure this is a consistent pattern.

Steps to Reproduce:

  1. Fill a bar with various quavers.
  2. Put focus on beat 1, hold down shift and arrow along. Notice it correctly announces each beat as you select and when you pause it announces the full range selection. Since 4.6 it has now started saying “stem” in front of each bar/beat reference, it would be much better if this just said the beat and only the bar when it changes and not “stem”.
  3. Add a hairpin from beats 2 to 3.5 (across 4 quavers).
  4. Put focus at the start of the bar and hold down shift while you arrow along the notes to select them. Notice that it announces the first two notes as above but once it hits the hairpin it announces “add next note to selection” with each arrow press. It also does not announce the full range selection when you pause or finish selecting and so the user has to try and count how many notes forward they have arrowed, very difficult over long passages.
Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.6.1

Regression

I was unable to check

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.

Research direction

The report names no source files or tests. Reproduce the range-selection steps in MuseScore Studio 4.6.1 on Windows with NVDA, including a hairpin, slur, or pedal mark, and compare announcements before and during the selection. Done means beats and range selections continue to be announced without repeated “add next” messages or the unwanted “stem” prefix.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
accessibility, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.