aboutsummaryrefslogtreecommitdiff
path: root/docs/getting-started/accessibility.md
diff options
context:
space:
mode:
authorMark Otto <[email protected]>2016-07-23 21:05:18 -0700
committerMark Otto <[email protected]>2016-07-23 21:05:18 -0700
commit7fd00263e35f891bfc792f9dd12c17a5025cd93c (patch)
tree28d07418fb7abfacccb317b501937e02ffccf096 /docs/getting-started/accessibility.md
parentd4457b33032d2540a4a3b7fa600f22055ce2000d (diff)
parent38312640df9c4b84a47e62d7dfeb16b25049aafb (diff)
downloadbootstrap-7fd00263e35f891bfc792f9dd12c17a5025cd93c.tar.xz
bootstrap-7fd00263e35f891bfc792f9dd12c17a5025cd93c.zip
Merge branch 'v4-dev' into v4-navbars
Diffstat (limited to 'docs/getting-started/accessibility.md')
-rw-r--r--docs/getting-started/accessibility.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/getting-started/accessibility.md b/docs/getting-started/accessibility.md
index 147d9305e..43dee3569 100644
--- a/docs/getting-started/accessibility.md
+++ b/docs/getting-started/accessibility.md
@@ -22,10 +22,10 @@ In addition, groups and toolbars should be given an explicit label, as most assi
## 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 (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).
+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).
{% callout danger %}
-Due to long-standing shortcomings/bugs in Chrome (see [issue 454172 in the Chromium bug tracker](https://code.google.com/p/chromium/issues/detail?id=454172 "Chromium bug tracker - Issue 454172: Focus Link Target (sequential focus navigation starting point)")) 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"`.
+Due to long-standing shortcomings/bugs in 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; }`.