I know, accessibility isn't the most important, but shouldn't be ignored for the final release - in sense of: what should be possible and what is realistic for the final release.
@Anatoly-os, OT: Thank's for the advice, but if I add the link [#...] oneself without any further comment from me, it seems to appear as comment and not in the section "what links here" of the initial entry. Or should I've a little bit patient?
edit: I think I've got it, I've to insert this link inside the related issue entries.
Comments
Thank's for creating this issue entry.
By filtering the issue tracker with the key word "accessibility" there are above some other entries:
https://musescore.org/en/project/issues/musescore?text=accessibility&st…
I didn't check them all (resp. my English skills are not enough in order to understand them correctly ;-).
Maybe for #273051: Keyboard shortcuts for palette objects there already exist a pull request.
For #47361: [Mac OS X] Insert measure keyboard shortcut doesn't exist, I don't know, how easy it could be to define a short cut by default.
I know, accessibility isn't the most important, but shouldn't be ignored for the final release - in sense of: what should be possible and what is realistic for the final release.
In reply to Thank's for creating this… by kuwitt
You can link the mentioned issues by yourself to this one by adding a link to this issue in the comments using [ # XXXXXX ] (without whitespaces)
.
@Anatoly-os, OT: Thank's for the advice, but if I add the link [#...] oneself without any further comment from me, it seems to appear as comment and not in the section "what links here" of the initial entry. Or should I've a little bit patient?
edit: I think I've got it, I've to insert this link inside the related issue entries.