musescore / musescore/MuseScore
Incomplete names of some symbols in the master palette
Open
@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
- Open MuseScore Studio.
- Create a score.
- Use the keyboard shortcut Shift+F9 to open the master palette.
- 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). - 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
- Link to video demonstration:
Bug_report_№5_(2024-08-07_14-42-16).mp4
https://disk.yandex.ru/i/tLJnPWA4OKjBNw
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
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.