Single tab keypress focus on map for keyboard users #358
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When one goes to the default map page, the first tabindex is set to the search field, which is good. But, to use the keyboard with the map (arrows for scrolling, =/- for zooming), one must press the tab key many times (26?). This modification quickly gets the keyboard to a much-used location via a single keypress. Perhaps another element should get a `tabindex="3"` attribute to minimize disruption; I've done only minimal focus-testing.
|
Merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When one goes to the default map page, the first tabindex is set to the search field, which is good. But, to use the keyboard with the map (arrows for scrolling, =/- for zooming), one must press the tab key many times (26?). This modification quickly gets the keyboard to a much-used location via a single keypress.
Perhaps another element should get a
tabindex="3"attribute to minimize disruption; I've done only minimal focus-testing.