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: Improve keyboard access #1734
Milestone
Comments
Shou
added a commit
that referenced
this issue
Sep 28, 2017
We make navigating with the tab key easier by highlighting focused elements more visibly, adding `tabindex` attributes to elements, and making `open-external` links respond to keyboard events. Change-Type: minor Changelog-Entry: Improve tab-key navigation through tabindex and visual improvements. Connects-To: #1734
Duplicate of #1745 |
Shou
added a commit
that referenced
this issue
Oct 25, 2017
We make navigating with the tab key easier by highlighting focused elements more visibly, adding `tabindex` attributes to elements, and making `open-external` links respond to keyboard events. Change-Type: minor Changelog-Entry: Improve tab-key navigation through tabindex and visual improvements. Connects-To: #1734
jhermsmeier
pushed a commit
that referenced
this issue
Oct 27, 2017
* feat(GUI): use tabindex and focus to navigate We make navigating with the tab key easier by highlighting focused elements more visibly, adding `tabindex` attributes to elements, and making `open-external` links respond to keyboard events. Change-Type: minor Changelog-Entry: Improve tab-key navigation through tabindex and visual improvements. Connects-To: #1734 * outline with 10s timeout * use orange "warning colour" as outline * smaller outline on settings buttons, fix order on settings page * allow selection in drive-selector * fix typo, better tabindexes
I guess this can be closed? |
Re-opening in light of #1854 |
Related to resin-io/hq#1024 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently accessing UI elements via the keyboard is certainly possible; but there's no visual indication of which element is active & selected.
We should add visual cues to allow for easy keyboard-only access & use.
The text was updated successfully, but these errors were encountered: