-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
tab-navigation incomplete/erroneous #4127
Comments
Could you clarify these?
What profile? |
Settings: selections dialog elements and switch elements are not focusable: Bildschirmaufnahme.2024-10-07.um.18.53.07.mp4 |
Selects are selectable in #4006 and probably in That's a pretty easy fix, I'll add that to #4006, so we don't drown in merges |
Partially addresses #4127 FYI the `@mixin button-reset` is actually only used in one place.
Partially addresses #4127 FYI the `@mixin button-reset` is actually only used in one place.
Partially addresses #4127 FYI the `@mixin button-reset` is actually only used in one place.
Partially addresses #4127 FYI the `@mixin button-reset` is actually only used in one place.
Partially addresses #4127 FYI the `@mixin button-reset` is actually only used in one place.
Partially addresses #4127 FYI the `@mixin button-reset` is actually only used in one place.
Partially addresses #4127 FYI the `@mixin button-reset` is actually only used in one place.
#4005 adds "tab navigation" to improve accessibility, so to help users who cannot or do not want to use a mouse.
the idea of the "tab navigation" is that it can replace a mouse completely.
however, there are some open ends with the navigation:
improvement: improve a11y #4133
improvement: arrow-key navigation for accounts list #4291
improvement: arrow-key navigation for chat list #4224
improvement: improve a11y #4210
improvement: a11y: arrow-key navigation for messages #4294
improvement: a11y: make settings keyboard-navigable #4319
sorry for nitpicking, but to make "tab navigation" useful, it should be coherent.
note, that "other shortcuts" are are more for power-users and are not a replacement for "tab navigation" issues: "tab navigation" should be useful without learning additional shortcuts, as said, being used as a mouse replacement
for further reading see eg. https://www.nngroup.com/articles/keyboard-accessibility/
The text was updated successfully, but these errors were encountered: