Skip link for keyboard/screen reader navigation #859
Closed
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
|
Isn't this already mostly available via the |
|
It is and I think skip links should be decided by the web developer based on the content that goes in the header and not be an absolute 'always present' link. |
|
here's some data on their use by AT users: http://webaim.org/projects/screenreadersurvey3/#skip thx for the PR, localpcguy, but we're gonna pass on this for now |
|
No problem, thanks for the consideration and the tip about the the . visuallyhidden and . visuallyhidden.focusable helper classes - I hadn't noticed those before. |
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.
Not sure if accessibility is one of the goals of h5bp, but if so, a skip link should be a pretty standard component for most websites to allow keyboard or screen reader to skip over the navigation menus directly to the content. More info at http://bit.ly/sOGGbb and http://bit.ly/sKG7PL.
If accessibility is not a current goal, then feel free to ignore/close this pull request.