musescore / musescore/MuseScore

String Numbers not shown in Braille Panel

Open
#34,238 0 comments 0 reactions 0 assignees View on GitHub

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

Currently in 4.7.4 a range of articulation, ornaments, bow markings, etc are shown in Braille. String numbers do not currently show.

STEPS:

  1. Add a note to a score and from the fingering palette choose a string number.
  2. Tab to the Braille panel and notice that the note has no extra sign with it.
    The Braille should show dots 146 (string sign) followed by the number (same as finger numbers) before the note.
    i.e. for violin:
    String 1 (E String) = 146, 1
    String 2 (A String) = 146, 12
    String 3 (D string) = 146, 123
    String 4 (G string) = 146, 2

Note that currently the speech is also incorrect on these as in the score it announces them as "finger 2", "finger 4", etc when they are actually string numbers. When adding them via the palette they do announce correctly in the pallette as "String 1", "String 2", etc. See #27954

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

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

Start by reproducing the issue from the fingering palette and checking the Braille panel, using the listed violin string-number mappings as the expected output. Verify that string numbers produce the 146 string sign followed by the correct number and that the score announces them as string numbers rather than finger numbers.

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
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.