-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
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
Incorrect accessibility interpretation for the skip nav link #12259
Comments
X-Ref: #12199 |
Unlike issue #12199 I am not recommending anything be changed in the bootstrap code base, I am suggesting they update their documentation to quit recommending people apply sr-only to an element that is not solely intended for screen readers. |
@programmer6 I get what you're saying now. Are you suggesting we switch to |
@mdo .hidden is just as bad as you can't tab to a hidden element my solution is generally to just make the skip nav link the same color as the background and then change it to something noticeable when it gains focus. @cvrebert that is interesting but maybe a bit complex I now wonder if the best solution is to just set the skip nav link color: rgba(0,0,0,0); then assign it's focused /active/hover classes a real color. Then it can have layout and position that remain unchanged (ie avoid the possibility of other things shifting around when it suddenly gains height and width). |
I'll also say that it clearly states in the WCAG 2.0 skip nav technique recommendation that leaving links visible at all times is preferred but then goes on to say hiding them when they do not have focus does meet the minimum criteria to be considered accessible. |
Proposed fix: #12679. |
The recommendation of applying the sr-only class to a skip navigation link is incorrect:
http://getbootstrap.com/getting-started/#accessibility
Someone has misinterpreted the intent of a skip navigation link, one of the primary audiences for this are sighted people who are unable to use a mouse (ie they are not using a screen reader). Part of this may be due to relying on 2nd hand information from the A11Y Project as opposed to just going straight to WCAG 2.0 guidelines:
http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html
A common implementation per WCAG 2.0 is to have a hidden link that becomes visible when it gains focus:
http://www.w3.org/TR/2013/NOTE-WCAG20-TECHS-20130905/G1
The text was updated successfully, but these errors were encountered: