musescore / musescore/MuseScore

No options to configure Braille output

Open
#28,342 0 comments 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

Since Jun 11, 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

This currently effects Braille export but as the Live Braille panel becomes less limited could effect that also, so designing something that has more settings for Braille output in the Braille preferences might work better than in the export dialogue itself.

Steps:

  1. Enter a score.
  2. Choose File → Export.
  3. From the list, choose Braille.

Notice there are no options to configure the braille output. In particular it would be good / essential to have:
• Braille page size (characters per line and lines per page)
• Braille language code (e.g. English UEB Contracted, Uncontracted, etc)
• Braille encoding (e.g. USA ASCII, Unicode)
• Music layout (e.g. Bar-over-bar, Section-by-section)
• Any other braille specific options (e.g. a filter for not showing certain musical signs).

A whole host of additional options for finer control could easily be imagined.

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

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.