diff options
Diffstat (limited to 'docs/getting-started/accessibility.md')
| -rw-r--r-- | docs/getting-started/accessibility.md | 13 |
1 files changed, 10 insertions, 3 deletions
diff --git a/docs/getting-started/accessibility.md b/docs/getting-started/accessibility.md index 1d60957ea..c1a23da35 100644 --- a/docs/getting-started/accessibility.md +++ b/docs/getting-started/accessibility.md @@ -7,13 +7,20 @@ Bootstrap follows common web standards and—with minimal extra effort—can be ### Skip navigation -If your navigation contains many links and comes before the main content in the DOM, add a `Skip to main content` link [before the navigation](http://a11yproject.com/posts/skip-nav-links/). Using the `.sr-only` class will visually hide the skip link, and the `.sr-only-focusable` class will ensure that the link becomes visible once focused (for sighted keyboard users). +If your navigation contains many links and comes before the main content in the DOM, add a `Skip to main content` link before the navigation (for a simple explanation, see this [A11Y Project article on skip navigation links](http://a11yproject.com/posts/skip-nav-links/)). Using the `.sr-only` class will visually hide the skip link, and the <code>.sr-only-focusable</code> class will ensure that the link becomes visible once focused (for sighted keyboard users). + +<div class="bs-callout bs-callout-danger" id="callout-skiplinks"> + <p>Due to long-standing shortcomings/bugs in Chrome (see <a href="https://code.google.com/p/chromium/issues/detail?id=262171" title="Chromium bug tracker - Issue 262171: Focus should cycle from named anchor">issue 262171 in the Chromium bug tracker</a>) and Internet Explorer (see this article on <a href="http://accessibleculture.org/articles/2010/05/in-page-links/">in-page links and focus order</a>), you will need to make sure that the target of your skip link is at least programmatically focusable by adding <code>tabindex="-1"</code>.</p> + <p>In addition, you may want to explicitly suppress a visible focus indication on the target (particularly as Chrome currently also sets focus on elements with <code>tabindex="-1"</code> when they are clicked with the mouse) with <code>#content:focus { outline: none; }</code>.</p> + <p>Note that this bug will also affect any other in-page links your site may be using, rendering them useless for keyboard users. You may consider adding a similar stop-gap fix to all other named anchors / fragment identifiers that act as link targets.</p> +</div> {% highlight html %} <body> <a href="#content" class="sr-only sr-only-focusable">Skip to main content</a> - <div class="container" id="content"> - The main page content. + ... + <div class="container" id="content" tabindex="-1"> + <!-- The main page content --> </div> </body> {% endhighlight %} |