musescore / musescore/MuseScore
Harmonic not shown in Braille Output
Open
Nobody has claimed this yet.
accessibility
community
- 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
Most other commonly used articulations, ornaments, bow markings, etc are now being shown in Braille. The harmonic is not.
STEPS:
- Add a note to a score and then from the Articulation palette select harmonic.
- Tab to the Braille panel and note that there is no sign added to the note to show it is a harmonic. This should be Brailled as dots 13 after the note and then the associated finger number (usually finger 3 or 4 for example in violin music).
Supporting files, videos and screenshots
N/A
In which versions of MuseScore Studio is this issue present?
4.7.4
Regression
No.
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by adding a harmonic from the Articulation palette, then checking the Braille panel with Windows 11 and NVDA. Compare its output with other articulations and verify that the harmonic is represented by dots 13 after the note followed by the associated finger number.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100