diff options
| author | Patrick H. Lauke <[email protected]> | 2015-02-21 14:05:01 +0000 |
|---|---|---|
| committer | Patrick H. Lauke <[email protected]> | 2015-02-21 14:05:01 +0000 |
| commit | 1194f0d481e2a76b21b845477a346375c9e3b98f (patch) | |
| tree | 1ff5945c6993a0d64816c5286b0cad7255b9a0c6 /docs/_includes/getting-started | |
| parent | 02f8cf9d0e3758d7fcffcda5ea7ba041b88b5e04 (diff) | |
| parent | b9504feb80d7fa95d84ef292097c270744aa4127 (diff) | |
| download | bootstrap-1194f0d481e2a76b21b845477a346375c9e3b98f.tar.xz bootstrap-1194f0d481e2a76b21b845477a346375c9e3b98f.zip | |
Merge pull request #15860 from patrickhlauke/url-fixup
Typo in URL
Diffstat (limited to 'docs/_includes/getting-started')
| -rw-r--r-- | docs/_includes/getting-started/accessibility.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/_includes/getting-started/accessibility.html b/docs/_includes/getting-started/accessibility.html index d43695ad3..df7206961 100644 --- a/docs/_includes/getting-started/accessibility.html +++ b/docs/_includes/getting-started/accessibility.html @@ -5,7 +5,7 @@ <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 (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>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> |