musescore / musescore/MuseScore
Braille Output: No dot 5 to indicate an editorial (invisible) item
Open
@shoogle is already working on this.
Since Jul 22, 2025.
accessibility
braille export
braille view
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
In Braille a dot 5 is put before any item that has been added by the editor/transcriber and is also used to signify an item that is invisible on the music notation score, in particular rests. These are not being used in the Braille panel and so a Braille reader can't tell for example that some rests in a certain voice are shown as invisible on the score.
- Create a bar with notes and some rests in both voice 1 &
- See how this looks on the Braille panel.
- Click on one of the rests and press V to make it invisible.
- Notice there is no change to the Braille. A dot 5 should be in front of any rests that are invisible.
- Now create a bar that has 4 crotchets in voice 1 and a minim on beats 1 & 2 of voice 2.
- Notice in the Braille panel the last cell is dots 136 for a minim rest.
- click on the minim rest in voice 2 and press delete to remove it.
- Notice that the Braille does not change. It should now have a dot 5 in front of it as it is an editorial rest added because Braille bars must add up, but there is now no rest on the print score, however, the Braille reader is unaware of this because in Braille it has not been marked as editorial.
Supporting files, videos and screenshots
N/A
What is the latest version of MuseScore Studio where this issue is present?
4.5.2
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.
Assessment
This issue has not been assessed yet.