musescore / musescore/MuseScore

No Speech Feedback when you respell a note

Open
#30,483 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
  1. Place focus on a note with an accidental, e.g. C#.
  2. Press J to respell.
    Notice the note changes to Db but there is no announcement from the screen reader. The user has to arrow off and on again to hear the change has in fact taken effect.
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

Reproduce the issue in MuseScore Studio on Windows 11 with NVDA: focus a note such as C#, press J, and verify that it changes to Db without an announcement. Trace the code handling the respell action and its accessibility feedback; done means the screen reader announces the new note spelling immediately.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.