Guidelines on this page will help you make your sites more
Aside from accessibility features that has been built into Foundation's components, this guide will give you additional best practices towards making your site more accessible. This is a living document and will continue to be updated.
-
Care about accessibility or want to contribute? Submit a Pull Request or get into the conversation on GitHub.
+
Care about accessibility or want to contribute? Submit a Pull Request or get into the conversation on GitHub.
`. Subsequent headings should make logical use of `
-
` such that screen readers can construct a table of contents for your pages.
+
+
Images should have text alternative for images. Captions or transcripts should be provided for video and audio. Sufficient color contrast between text and background is important for people with vision impairment or color blindness.
+
Sites should be navigatable using only a keyboard, providing meaningful hyperlinks, and allowing enough time for users to complete a task.
+
Make content readable and provide predictable functionality.
+
Maximizing compatibility with current and future tools (web browsers, assistive technologies, etc.).
+
+
+***
+## Keyboard Access
+
+
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,
-click into the browser address bar.
+### How to Test a Website’s Keyboard Accessibility
-Take your hand off your mouse and use only your keyboard.
-Using the Tab button, navigate until you’ve reached the link below. (You can use Shift+Tab to navigate back one step.)
+
On a desktop or laptop in Firefox, IE, Chrome, or Safari,
+click into the browser address bar.
+
+
Take your hand off your mouse and use only your keyboard.
+Using the Tab button, navigate until you’ve reached the link below. (You can use Shift+Tab to navigate back one step.)
Right arrow: Next navigation bar item
@@ -27,11 +56,70 @@
Guidelines on this page will help you make your sites more
Enter: Activate currently focused item (i.e. navigate to corresponding URL)
Give the person the ability to skip the navigation at the top of the page. If you have menu with 40 links, you can imagine how long it would take someone to tab through all that. Here's one way to do it:
\ No newline at end of file
diff --git a/doc/pages/components/dropdown_buttons.html b/doc/pages/components/dropdown_buttons.html
index 37f338821f..504ada3841 100644
--- a/doc/pages/components/dropdown_buttons.html
+++ b/doc/pages/components/dropdown_buttons.html
@@ -33,32 +33,13 @@
Rendered HTML
Advanced
-Additional classes can be added to your dropdown buttons to change their appearance.
+Additional classes can be added to your dropdown buttons to change their appearance and behavior.
-