diff options
Diffstat (limited to 'docs/getting-started')
| -rw-r--r-- | docs/getting-started/accessibility.md | 6 | ||||
| -rw-r--r-- | docs/getting-started/browsers-devices.md | 2 | ||||
| -rw-r--r-- | docs/getting-started/build-tools.md | 2 | ||||
| -rw-r--r-- | docs/getting-started/contents.md | 2 |
4 files changed, 6 insertions, 6 deletions
diff --git a/docs/getting-started/accessibility.md b/docs/getting-started/accessibility.md index d7ecd8cec..9b2fc37db 100644 --- a/docs/getting-started/accessibility.md +++ b/docs/getting-started/accessibility.md @@ -23,7 +23,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 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"`. @@ -47,10 +47,10 @@ Note that this bug will also affect any other in-page links your site may be usi When nesting headings (`<h1>` - `<h6>`), your primary document header should be an `<h1>`. Subsequent headings should make logical use of `<h2>` - `<h6>` such that screen readers can construct a table of contents for your pages. -Learn more at [HTML CodeSniffer](https://squizlabs.github.io/HTML_CodeSniffer/Standards/Section508/) and [Penn State's Accessability](http://accessibility.psu.edu/headings). +Learn more at [HTML CodeSniffer](https://squizlabs.github.io/HTML_CodeSniffer/Standards/Section508/) and [Penn State's Accessability](http://accessibility.psu.edu/headings/). ## Additional resources - ["HTML Codesniffer" bookmarklet for identifying accessibility issues](https://github.com/squizlabs/HTML_CodeSniffer) - [The A11Y Project](http://a11yproject.com/) -- [MDN accessibility documentation](https://developer.mozilla.org/en-US/docs/Accessibility) +- [MDN accessibility documentation](https://developer.mozilla.org/en-US/docs/Web/Accessibility) diff --git a/docs/getting-started/browsers-devices.md b/docs/getting-started/browsers-devices.md index 842092ccf..d21024594 100644 --- a/docs/getting-started/browsers-devices.md +++ b/docs/getting-started/browsers-devices.md @@ -168,7 +168,7 @@ Confirm the document mode by opening the debugging tools: press <kbd>F12</kbd> a This tag is included in all of Bootstrap's documentation and examples to ensure the best rendering possible in each supported version of Internet Explorer. -See [this StackOverflow question](https://stackoverflow.com/questions/6771258/whats-the-difference-if-meta-http-equiv-x-ua-compatible-content-ie-edge) for more information. +See [this StackOverflow question](https://stackoverflow.com/questions/6771258/what-does-meta-http-equiv-x-ua-compatible-content-ie-edge-do) for more information. ## Internet Explorer 10 in Windows Phone 8 diff --git a/docs/getting-started/build-tools.md b/docs/getting-started/build-tools.md index a6d0593fa..e62961663 100644 --- a/docs/getting-started/build-tools.md +++ b/docs/getting-started/build-tools.md @@ -11,7 +11,7 @@ Bootstrap uses [Grunt](http://gruntjs.com) for its CSS and JavaScript build syst To use our Gruntfile and run our documentation locally, you'll need a copy of Bootstrap's source files, Node, and Grunt. Follow these steps and you should be ready to rock: -1. [Download and install Node](https://nodejs.org/download), which we use to manage our dependencies. +1. [Download and install Node](https://nodejs.org/download/), which we use to manage our dependencies. 2. Install the Grunt command line tools, `grunt-cli`, with `npm install -g grunt-cli`. 3. Navigate to the root `/bootstrap` directory and run `npm install` to install our local dependencies listed in [package.json](https://github.com/twbs/bootstrap/blob/master/package.json). 4. [Install Ruby][install-ruby], install [Bundler][gembundler] with `gem install bundler`, and finally run `bundle install`. This will install all Ruby dependencies, such as Jekyll and plugins. diff --git a/docs/getting-started/contents.md b/docs/getting-started/contents.md index 4f51ef049..682c2310c 100644 --- a/docs/getting-started/contents.md +++ b/docs/getting-started/contents.md @@ -25,7 +25,7 @@ bootstrap/ └── bootstrap.min.js {% endhighlight %} -This is the most basic form of Bootstrap: precompiled files for quick drop-in usage in nearly any web project. We provide compiled CSS and JS (`bootstrap.*`), as well as compiled and minified CSS and JS (`bootstrap.min.*`). CSS [source maps](https://developer.chrome.com/devtools/docs/css-preprocessors) (`bootstrap.*.map`) are available for use with certain browsers' developer tools. +This is the most basic form of Bootstrap: precompiled files for quick drop-in usage in nearly any web project. We provide compiled CSS and JS (`bootstrap.*`), as well as compiled and minified CSS and JS (`bootstrap.min.*`). CSS [source maps](https://developers.google.com/web/tools/chrome-devtools/javascript/source-maps) (`bootstrap.*.map`) are available for use with certain browsers' developer tools. ## Bootstrap source code |