diff options
| author | Patrick H. Lauke <[email protected]> | 2015-02-04 15:38:17 +0000 |
|---|---|---|
| committer | Patrick H. Lauke <[email protected]> | 2015-02-04 15:38:17 +0000 |
| commit | 27677fab5b704d8c61c4561dd7dd55d54fbcc8f2 (patch) | |
| tree | 1bd14c7686fee9a7fd429d05c81fb08f57129f60 /docs/_includes | |
| parent | 0e40c818d9e27d35034b7872ac34d2fa5a886734 (diff) | |
| parent | 214516da16c99c7118b29ecef3bdf10f977d4e29 (diff) | |
| download | bootstrap-27677fab5b704d8c61c4561dd7dd55d54fbcc8f2.tar.xz bootstrap-27677fab5b704d8c61c4561dd7dd55d54fbcc8f2.zip | |
Merge pull request #15714 from patrickhlauke/skip-link-fixes
Skip link workarounds for Chrome and IE
Diffstat (limited to 'docs/_includes')
| -rw-r--r-- | docs/_includes/getting-started/accessibility.html | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/docs/_includes/getting-started/accessibility.html b/docs/_includes/getting-started/accessibility.html index cbb528dce..d43695ad3 100644 --- a/docs/_includes/getting-started/accessibility.html +++ b/docs/_includes/getting-started/accessibility.html @@ -3,12 +3,17 @@ <p class="lead">Bootstrap follows common web standards and—with minimal extra effort—can be used to create sites that are accessible to those using <abbr title="Assistive Technology" class="initialism">AT</abbr>.</p> <h3>Skip navigation</h3> - <p>If your navigation contains many links and comes before the main content in the DOM, add a <code>Skip to main content</code> link before the navigation <a href="http://a11yproject.com/posts/skip-nav-links/">(read why)</a>. Using the <code>.sr-only</code> 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).</p> + <p>If your navigation contains many links and comes before the main content in the DOM, add a <code>Skip to main content</code> link before the navigation (for a simple explanation, see this <a href="http://a11yproject.com/posts/skip-nav-links/">A11Y Project article on skip navigation links</a>). Using the <code>.sr-only</code> 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).</p> + <div class="bs-callout bs-callout-danger" id="callout-tables-striped-ie8"> + <p>Due to long-standing shortcomings/bugs in Chrome (see <a href="https://code.google.com/p/hromium/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"> + <div class="container" id="content" tabindex="-1"> <!-- The main page content --> </div> </body> |