diff options
| author | Mark Otto <[email protected]> | 2015-04-16 16:56:40 -0700 |
|---|---|---|
| committer | Mark Otto <[email protected]> | 2015-04-16 16:56:40 -0700 |
| commit | 466d36e54175ee00927d6518d9481acd2d210590 (patch) | |
| tree | b24687c6657e786c372a4467d059ca064b590dbb /docs/getting-started/accessibility.md | |
| parent | 801d49fb32ffe03a9cc9fd4225896d747b37a0a5 (diff) | |
| download | bootstrap-466d36e54175ee00927d6518d9481acd2d210590.tar.xz bootstrap-466d36e54175ee00927d6518d9481acd2d210590.zip | |
Redo all our callouts with the custom callout plugin
- Replaces manual use of .bd-callout with {% callout [type] %}
- Rearranged some callouts for proximity to others
- Turned long lists of callouts--like those on tooltips, plugings, etc--into a list because holy shit that's overwhelming
Diffstat (limited to 'docs/getting-started/accessibility.md')
| -rw-r--r-- | docs/getting-started/accessibility.md | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/docs/getting-started/accessibility.md b/docs/getting-started/accessibility.md index 25bc36acc..47f24d8dd 100644 --- a/docs/getting-started/accessibility.md +++ b/docs/getting-started/accessibility.md @@ -9,11 +9,13 @@ Bootstrap follows common web standards and—with minimal extra effort—can be 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="bd-callout bd-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> +{% callout danger %} +Due to long-standing shortcomings/bugs in Chrome (see [issue 262171 in the Chromium bug tracker](https://code.google.com/p/chromium/issues/detail?id=262171 "Chromium bug tracker - Issue 262171: Focus should cycle from named anchor")) and Internet Explorer (see this article on [in-page links and focus order](http://accessibleculture.org/articles/2010/05/in-page-links/)), you will need to make sure that the target of your skip link is at least programmatically focusable by adding `tabindex="-1"`. + +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 `tabindex="-1"` when they are clicked with the mouse) with `#content:focus { outline: none; }`. + +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. +{% endcallout %} {% highlight html %} <body> |