Open VladislavBuyalski opened 1 month ago
Full list of categories and symbols with incomplete names: Brackets (all symbols)
Lines (16 symbols): 2 symbols - Hairpin: Crescendo 2 symbols - Hairpin: Custom 2 symbols - Volta: 2 6 symbols - Pedal 4 symbols - Text line
Barlines (5 symbols): 5 symbols - Barline: Single barline
Arpeggios & Glissandos (8 symbols): 6 symbols - Arpeggio 2 symbols - Glissando
Text (2 symbols): 2 symbols - Text line
Tempo (11 symbols): 11 symbols - Gradual tempo change
Dynamics (4 symbols): 2 symbols - Hairpin: Custom 2 symbols - Hairpin: Crescendo
Repeats & Jumps (2 symbols): 2 symbols - Volta: 2
Bagpipe embellishments (all symbols)
Layout (7 symbols): 4 symbols - Layout break 3 symbols - Spacer
This bug report also applies to all symbols that have the same name "Action icon". I have submitted a bug report about this before: https://github.com/musescore/MuseScore/issues/23523
I would like to work on this issue.
If there is anything I can do to help you, you can always let me know.
@shubham-shinde-442, you just need to make sure these elements all have unique accessible names. The tooltips appear to be unique for many of these, so that's a good place to start. But if the tooltip is "Single barline", the accessible name should be "Barline: single". Also, "Barline: start repeat" is better than "Barline: left repeat".
And if several symbols have the same name, we would be happy to hear the unique differences between these symbols. Maybe there are visual differences, or for example the direction, like for the arpeggio symbols, up or down, Straight line or wavy, etc.
@VladislavBuyalski @shoogle Probably both the hairpin symbols, such as Crescendo, and custom already have unique accessible names. If not, please explain
I think that similar symbol names may contain information about visual differences. For example, line type (straight, wavy, dotted) etc. direction (up, down, right to left, left to right) etc. For tempo, slowing down or speeding up, for pedal, lifting or pressing, etc.
Issue type
Accessibility issue (e.g. for keyboard-only or screen reader users)
Description with steps to reproduce
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