Project properties dialog - accessibility/usability issue
There is no way to use the keyboard to Tab between fields on the Project properties dialog. For accessibility, all fields should be accessible in a logical order via the Tab key. For usability, I prefer to use my keyboard as much as possible, I should be able to type the Work title, Tab to the next field, type the Subtitle, etc., eventually ending up at the OK button. Currently, no matter which field you are typing in, when you hit the Tab key, your cursor jumps right to the OK button.
Comments
Known issue. Use the arrow keys instead
In reply to Known issue. Use the arrow… by Jojo-Schmitz
Is there an open bug for it? Tab key is the standard for applications and web browsers, users may not think to use the arrow keys.
Windows: "To receive focus (without using a pointer), the control must be accessible through tab navigation" https://learn.microsoft.com/en-us/windows/apps/design/accessibility/key…
Mac: "Move to the next UI element: Press the Tab key." http://support.apple.com/en-ca/guide/mac-help/mchlc06d1059/mac
WCAG: "interactive elements are navigated using the tab key" https://www.w3.org/TR/WCAG20-TECHS/H4.html
In reply to Is there an open bug for it?… by tenvolt
It's not a bug; it's intentional.
They are trying to adhere to some "accessibility standard" ... that is not standard by any measure I can find, or even documented anywhere as far as I can find. There was a whole long discussion (several long discussions?) of this last summer or the year before. :-(
In reply to It's not a bug; it's… by TheHutch
That's odd. Do you have a link out of curiosity? The 3 references show that "Tab" is the standard, it's even referred to as "tab order". Adding the ability to use the arrow keys is fine as another option, but not supporting the Tab key is not best practice nor consistent with pretty much anything else that is out there, and creates obstacles or unnecessary learning curves for users, especially when the help seems woefully out of date. Would love to see some evidence of usability or accessibility testing supporting these changes as opposed to them just being executive or "loudest voice wins" decisions.
In reply to That's odd. Do you have a… by tenvolt
No, that's what I meant by "that is not ... even documented anywhere as far as I can find". Users more experience than I (and I am very experienced) and developers repeatedly informed me that this was "the new standard" but never provided any documentation for this so-called standard.
I agree with you whole-heartedly, but have given up arguing about the matter. *shrug*
Now I just bitch about it :-) like this post :-D
In reply to Is there an open bug for it?… by tenvolt
See https://github.com/musescore/MuseScore/issues/27498
In reply to See https://github.com… by Jojo-Schmitz
Fairly recent. This was discussed in the forums and in the Github much more ... robustly :-) last summer sometime. Notice, however, that no attempt is made to provide documentation for this (non-standard!) "hierarchical navigation model". It never was last summer either. It was merely claimed that this was a new standard, supposedly used by many other applications (though, again, none were identified), adopted to ease Accessibility.
I should say that, when I say "last summer", it may have been summer 2024, or it may have been summer 2023. I'm not sure.
In reply to Known issue. Use the arrow… by Jojo-Schmitz
Arrow keys do not work in many different situations on this dialog, e.g. multiline text, and they are implemented almost randomly, sometimes you need to hit up-arrow, sometimes down, sometimes left, and the arrows go through unrelated things like the "Folder" button and the text fields.