Improved general navigation for screen readers #702
Merged
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
…heme - added hidden navigation menu - hidden TabBar from screen readers - auto focus for the back button on forward navigation - added a11y sections to the category page - improved visibility of engage/core hocs in the developer tools
…ibility-basic-navigation
…t render properly
SG-Noxoreos
approved these changes
Jun 19, 2019
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.
Description
This ticket is about to improve the general navigation for screen readers at both themes. It introduces a main menu which is only accessible via a screen reader. Additionally it introduces auto focus at the navigation bar on forward navigation, and it highlights the two content sections of category pages.
Type of change