musescore / musescore/MuseScore

Incomplete names of some symbols in the master palette

Open
#23,949 8 comments 1 reaction 2 assignees View on GitHub

@shubham-shinde-442 is already working on this.

Since Aug 11, 2024.

accessibility community P2
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
  • NVDA screen reader is used
  1. Open MuseScore Studio.
  2. Create a score.
  3. Use the keyboard shortcut Shift+F9 to open the master palette.
  4. The following categories contain some symbols that have incomplete names:
    Brackets (all symbols), Lines (16 symbols), Barlines (5 symbols), Arpeggios & Glissandos (8 symbols), Text (2 symbols), Tempo (11 symbols), Dynamics (4 symbols), Repeats & Jumps (2 symbols), Bagpipe embellishments (all symbols), Layout (7 symbols).
  5. When choosing some symbols from these categories, we do not know their type, direction or other visual features of these symbols. After adding the description, we can understand what the symbol looks like visually and which symbol we should use among many with the same name.
Supporting files, videos and screenshots
What is the latest version of MuseScore Studio where this issue is present?

MuseScore Studio 4.3.2

Regression

No.

Operating system

Windows 10 (64 bit)

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.