musescore / musescore/MuseScore

No Braille output of Trill line

Open
#34,356 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accessibility braille export braille view 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

STEPS:

  1. Add a trill line from the ornaments panel to a note.
  2. Notice there is no change to the Braille. The note still shows as before. The sign for the trill is not added.

See also #34355 as this is not being output correctly with screen reader speech also.

Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.7.4

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 from the ornaments panel by adding a trill line to a note, then inspect the resulting Braille output and compare the related screen-reader issue in #34355. Done means the Braille representation includes the trill sign for the affected note.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
accessibility
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.