musescore / musescore/MuseScore

Additional speech needed when navigating percussion notation

Open
#32,802 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accessibility needs design P2
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

Currently a blind user has no easy way to know what their percussion music looks like in print on the score. For other instruments this added info is not required as as long as you know the clef you know the space/line position. However, as percussion scoring can vary this info is required.

This could be done in one of two ways (or both):

  1. Add the additional info of line/space, stem direction and note head shape at the end of the string of info spoken as you arrow along the score notes. So for example "Bass Drum 1, crotchet, voice 2, bar 1 beat 1, space 1, filled note head, stem down". As voices are announced maybe the stem down isn't necessary, but the line/space is the crucial missing bit and the X or circled heads.
  2. These could be discovered by going to the Percussion panel and changing to Notation Preview instead of pad name. See #32788.
Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.7 beta

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

Start by reproducing the issue in MuseScore Studio 4.7 beta with NVDA, checking the speech produced while arrowing through percussion notes. Compare that with the Percussion panel's Notation Preview option described in #32788; the work is done when blind users can discover the relevant percussion notation details, including line or space and notehead shape.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.