From 466d36e54175ee00927d6518d9481acd2d210590 Mon Sep 17 00:00:00 2001 From: Mark Otto Date: Thu, 16 Apr 2015 16:56:40 -0700 Subject: 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 --- docs/getting-started/accessibility.md | 12 +++++++----- docs/getting-started/contents.md | 9 +++++---- docs/getting-started/javascript.md | 9 +++++---- 3 files changed, 17 insertions(+), 13 deletions(-) (limited to 'docs/getting-started') 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 .sr-only-focusable 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 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 %} diff --git a/docs/getting-started/contents.md b/docs/getting-started/contents.md index 811c60f44..3bfbafb4c 100644 --- a/docs/getting-started/contents.md +++ b/docs/getting-started/contents.md @@ -5,10 +5,11 @@ title: Contents Bootstrap can come in one of two forms, as precompiled or source code. Learn more about each form's contents and structure below. -
-

jQuery required

-

Please note that all JavaScript plugins require jQuery to be included, as shown in the starter template. Consult our bower.json to see which versions of jQuery are supported.

-
+{% callout warning %} +#### jQuery required + +Please note that **all JavaScript plugins require jQuery** to be included, as shown in the [starter template](../quick-start). [Consult our `bower.json`]({{ site.repo }}/blob/v{{ site.current_version }}/bower.json) to see which versions of jQuery are supported. +{% endcallout %} ### Precompiled Bootstrap diff --git a/docs/getting-started/javascript.md b/docs/getting-started/javascript.md index eafa473d5..759c2b807 100644 --- a/docs/getting-started/javascript.md +++ b/docs/getting-started/javascript.md @@ -87,10 +87,11 @@ $.fn.tooltip.Constructor.VERSION // => "{{ site.current_version }}" Bootstrap's plugins don't fall back particularly gracefully when JavaScript is disabled. If you care about the user experience in this case, use [`