-
-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessibility: focused widgets not visually distinguishable #297
Comments
Indeed; that was a bit unfair of me. But the equivalent CSS selector for |
Thanks for investigating; indeed there are some focus cues, but I wouldn't call that "everything" :-) |
Expected behaviour
When using keyboard navigation, it’s paramount that one can tell
where the focus currently is. Many of the provided themes do not
currently allow that.
Actual behaviour
Let’s play “where’s the focus”. I’ve provided two test cases: one
with a minimal GtkStackSwitcher interface, the other one with a
real-world example (in this case Inkscape).
In the first example, the page opened is obviously the first one
(numbered 0), but the keyboard focus is actually on the second
tab button.
The second example is with a real-world application (in this case, Inkscape):
here the focus is actually on the second combobox dropdown button “mm”,
in the “Custom size” section. (You could be led to believe that it’s in the
previous entry field “Height”, but it’s not.)
As you can see, the only theme that scores well in both cases is really
HighContrast (even HighContrastInverted fails in the second round.)
BlueMenta is also actually fairly usable; as for the Submarines, they
have no notion of any focus whatsoever.
Steps to reproduce the behaviour
If you want to play at home:
download the minimal GtkStack example I provided,
launch it using
glade-previewer
,hit the Right arrow twice to reach the second tab
(if you’re not sure as to said focus actually moved, hit Space to confirm).
Next up, fire up Inkscape,
open the Document properties dialog (Ctrl-Shift-D),
Hit Tab seven times to reach the second combo box.
MATE general version
Reproduced with both 1.20 and master.
The text was updated successfully, but these errors were encountered: