Hello everyone! I saw that the accessibility for palettes is one of the points in the roadmap for MuseScore 2.1 [0], so I revisited the implementation I started some time ago. I know that Lasconic had the idea to make the palettes searchable and I think that it is a great idea for accessibility since it will speed up the process of score editing for keyboard users and that Marc made it possible for all elements to be added to the score without drag and drop which was a huge step.
My implementation provides the ability to traverse palette elements with the keyboard, while keeping the palettes stateless in the rest of the time and provides screen-reader feedback for each selection change. It works in the palettes from the main window, the master palette (although it needs a bit of fine tweaking here to make things perfect) and in the key signature palette from the create new score dialog. Everything can be found in this branch [1] . I've also started in the past to add shortcuts to jump to each individual palette, but if the palettes become searchable I think this will redundant and MuseScore already has a lot of shortcuts, so it would be hard to find meaningful ones. Even if the palettes will be searchable, I still believe that users should be able to traverse the palettes using only the keyboard, so that can learn what is there in the first place. Any feedback would be very appreciated. :) Thank you, Andrei Tuicu [0] https://musescore.org/en/developers-handbook/references/musescore-roadmap#Accessibility [1] https://github.com/andreituicu/MuseScore/tree/accessible_palettes
------------------------------------------------------------------------------
_______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
