From 3502c478f1c6b8eece56f4eeef377fab752b494f Mon Sep 17 00:00:00 2001 From: Joe Watkins Date: Thu, 27 Aug 2015 08:44:39 -0700 Subject: [PATCH] Docs - Remove Tabindex section --- doc/pages/accessibility.html | 19 ------------------- 1 file changed, 19 deletions(-) diff --git a/doc/pages/accessibility.html b/doc/pages/accessibility.html index 164ec842b..3ac18e620 100644 --- a/doc/pages/accessibility.html +++ b/doc/pages/accessibility.html @@ -23,25 +23,6 @@ Aside from accessibility features that has been built into Foundation's componen

The most common impairments for web users are those with problems seeing, hearing or a physical inability to use a mouse. For that reason, the site must be navigatable by keyboard. Most commonly the tab key is used to tab through the content. For a vision impaired person will have a screenreader installed that reads the content out loud. We used Chromevox to test with. You can find a list of popular screen readers below in the resource list.

-### Tab-index - -

Tab index lets users move forward and backward through the links and form elements on a page. But you can make anything "tabbable" with the tabindex attribute. - -{{#markdown}} -```html -

…

- -
…
- - -``` -{{/markdown}} - -

As the numbers suggest, tapping on the tab key takes users through anything with the tabindex attribute in order. In HTML5, you can use it on any element. That means you can set priorities quickly. Want to help people get past the same tedious navigation they get on every page? Use tabindex to put navigation last.

- -

Tip: When starting out use sets of 10: tabindex="10", tabindex="20", tabindex="30". If you decide to rearrange the order — say, put the third item between the first and second — you don't have to rearrange everything. Just make it tabindex="15".

- - ### How to Test a Website’s Keyboard Accessibility

On a desktop or laptop in Firefox, IE, Chrome, or Safari, -- 2.47.2