W3 Accessibility Guidelines Core
Audio-only and Video-only Time Based Media
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints
The intent of this Success Criterion is to ensure that, wherever possible, content can be operated through a keyboard or keyboard interface (so an alternate keyboard can be used). When content can be operated through a keyboard or alternate keyboard, it is operable by people with no vision (who cannot use devices such as mice that require eye-hand coordination) as well as by people who must use alternate keyboards or input devices that act as keyboard emulators. Keyboard emulators include speech input software, sip-and-puff software, on-screen keyboards, scanning software and a variety of assistive technologies and alternate keyboards. Individuals with low vision also may have trouble tracking a pointer and find the use of software much easier (or only possible) if they can control it from the keyboard.
W3 Accessibility Guidelines Static-Web
The objective of this technique is to use standard HTML form controls and link elements to provide keyboard operation and assistive technology interoperability of interactive user interface elements.
User agents provide the keyboard operation of HTML form controls and links. In addition, the user agent maps the form controls and links to an accessibility API. Assistive technologies use the accessibility API to extract appropriate accessibility information, such as role, name, state, and value, and present them to users. The role is provided by the HTML element, and the name is provided by the text associated with that element. Elements for which values and states are appropriate also expose the values and states via multiple mechanisms.
In some cases, the text is already associated with the control through a required attribute. For example, submit buttons use the button element text or image 'alt' attribute as the name. In the case of form controls, label elements or 'title' attributes are used. The following table describes how the role, name, value, and state are determined for HTML links and form controls.
| HTML element | Role | Name | Value | State |
|---|---|---|---|---|
| <a> | link | 'title' attribute, text within <a> element or 'alt' attribute if image link. Concatenated if both text and image 'alt' attribute are provided | 'href' attribute | |
| <button> | push button | text inside <button> element or 'title' attribute | ||
| <fieldset> | grouping | text inside <legend> element within fieldset element | ||
| <input type = "button", "submit", or "reset"> | push button | 'value' attribute | ||
| <input type = "image"> | push button | 'alt' attribute or 'title' attribute | ||
| <input type = "text"> | editable text | <label> element associated with it or 'title' attribute | 'value' attribute | |
| <input type = "password"> | editable text | <label> element associated with it or 'title' attribute | value is purposefully hidden | |
| <input type="file"> | editable text | <label> element associated with it or 'title' attribute | 'value' attribute | |
| <input type="checkbox"> | checkbox | <label> element associated with it or 'title' attribute | 'checked' attribute | |
| <input type="radio"> | radio button | <label> element associated with it or 'title' attribute | 'checked' attribute | |
| <select> | list box | <label> element associated with it or 'title' attribute | <option> element with 'selected' attribute set to "selected" | |
| <textarea> | editable text | <label> element associated with it or 'title' attribute | text within <textarea> element |