aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCurt Grimes <[email protected]>2016-06-23 22:39:03 -0500
committerChris Rebert <[email protected]>2016-06-23 23:15:38 -0700
commit76e9a7328efd364e747c2e71b9cad5c44a3b5ecd (patch)
tree88c98d6b661cfde1cbe4bb06ec0a214e34ad37c3 /docs
parentd39e24347c2dea7bb526a144610ed532f167bd40 (diff)
downloadbootstrap-76e9a7328efd364e747c2e71b9cad5c44a3b5ecd.tar.xz
bootstrap-76e9a7328efd364e747c2e71b9cad5c44a3b5ecd.zip
Fix links to A11Y Project posts
Closes #20165 [skip sauce]
Diffstat (limited to 'docs')
-rw-r--r--docs/getting-started/accessibility.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/getting-started/accessibility.md b/docs/getting-started/accessibility.md
index 147d9305e..9faaaffb1 100644
--- a/docs/getting-started/accessibility.md
+++ b/docs/getting-started/accessibility.md
@@ -22,7 +22,7 @@ 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"`.