Each Guideline and each Technique has a priority listed. For the guidelines, the priority refers to the importance of addressing the issue identified by the guideline. For Techniques, there may be a number of techniques used to improve accessibility with respect to this guideline. For example a priority 1 Guideline may have a priority 1 Technique, which MUST be done to provide accessibility, and a priority 3 Technique, which MAY also be done to help address the issue.
Rationale: Otherwise, users who are blind, have low vision, or have chosen not to view graphics will not know the purpose of the visual components on the page. Example
Since ASCII art uses characteres to create a visual image there is no way to attach alt-text as with other images.
Techniques:
Rationale: Otherwise, important information presented graphically (charts, billboards, diagrams) will not be perceivable to people with blindness, some people with low vision, and users who have chosen not to view graphics, scripts, or applets or whose browser does not support scripts or applets.
Techniques:
Rationale: Otherwise, users who are deaf, or hard of hearing, or who have sound turned off cannot perceive the information presented through sounds such as speech, sound effects, and music.
Techniques:
Rationale: Otherwise, users who cannot see (or look at) the page will not be able to perceive information presented through action, body language, or other visual cues that are not available through the auditory information (dialogue, sound effects, etc.). The collated text version allows access to the information by devices that do not play movies, by people who are deaf-blind. (It also allows all of the content to be accessed by indexing engines.)
Techniques:
Rationale: For example, if you use an image as the source of a frame, then there is no simple way to attach alternative text for that image. But, if you use an HTML file as the source of a frame with the image included in that, providing the alternative text becomes easy. (see A-1 for more information about alt-text).
Techniques:
Rationale: If color is used to convey information, those who cannot differentiate between certain colors (and those with devices that have non-color or non-visual displays) will not receive the information.
Techniques:
Quick test: Is your page viewable and understandable in monochrome?
Rationale: When content is tied to presentation, such as color-coding list items to distinguish between them in some way, it is difficult to impossible to transform the information into a different modality. Example.
Character spacing and non-letter characters cause problems for screen readers.
Techniques:
Rationale: When elements and attributes are used inappropriately, such as using structural elements for presentation purposes (e.g., H1 to create large, bold face text on some location other than a heading), user agents that allow users to navigate through the structure will be unable to do so properly. Reformatting the page for other media and devices can also be difficult.
Techniques:
Rationale: Some people with cognitive limitations or visual disabilities are unable to read moving text quickly enough or at all. Movement can also cause such a distraction that the rest of the page becomes unreadable for people with cognitive disabilities. Screen readers are unable to read moving text. People with physical disabilities might not be able to move quickly or accurately enough to interact with moving objects. People with photosensitive epilepsy can have seizures triggered by flickering or flashing in the 4 to 59 hertz range with a peak sensitivity at 20hz.
Techniques:
Note. Avoid BLINK and MARQUEE since they are proprietary elements. See E-1
Rationale: When forground and background colors are too close to the same hue, they may not provide sufficient contrast when viewed using monochrome displays or by people with different types of color blindness.
Techniques:
Quick test: Is your page viewable and understandable in monochrome?
Rationale: This is a particular problem for braille translators, especially when multiple languages appear on the same page.
Techniques:
Rationale: With each release of HTML new features have been added. In the recent past, new features have incorporated new technologies such as the ability to attach style sheets to a page or to embed scripts and applets in a page. Older browsers ignore new features and some users configure their browser not to make use of new features. These users often see nothing more than a blank page or an unreadable page when new features do not fail gracefully.
Techniques:
Techniques:
See also E-5 - text-only pages.
Rationale: Someone who is using the page without sight, with voice input, or with a keyboard (or input device other than a mouse) will have a difficult time navigating a page if keyboard shortcuts are not provided for objects on the page. Access to image maps is impossible for these users if alternatives are not provided.
Techniques:
Rationale: Older browsers are unable to "Tab" to edit boxes, text areas and lists of consecutive links, making it difficult to impossible for users to access them.
Users not operating in a graphical environment are disoriented by being transferred to a new window without warning.
Until most users are able to secure newer technologies that address these issues:
Techniques:
Rationale: Users with blindness and low vision often access the screen with "tunnel vision" and are unable to get an overview understanding of the page. Complex intertwinings of frames may also be difficult for people with cognitive disabilities to use.
Techniques:
Rationale: Unless expansions for abbreviations and acronyms are provided they may be indecipherable when spoken or brailled.
Techniques:
Rationale: This provides contextual information about the relationship between controls, which is useful for all users.
Techniques:
Rationale:
Many user agents restructure tables to present them. Without appropriate markup the tables will not make sense when restructured. Tables also present special problems to users of screen-readers.
These guidelines benefit users that are accesing the table auditorally or viewing only a portion of the page at a time (users with blindness and low vision, or using an auto-pc, or devices with small displays)
Techniques:
Rationale: Otherwise people who use your site who are blind, or have difficulty seeing, or are using devices that do not have displays or very small displays will have difficulty. If they are moving from link to link, and a link phrase does not make sense, they will then have to stop and read the text around the link in order to discover what it means.
Techniques:
Rationale: By avoiding elements that can only be interpreted by a specific browser type, your pages will be able to be accessed by more people across a larger number of hardware and software devices.
Use a "composit" checker that can test for multiple HTML specifications simultaneouly such as_______________ or Bobby [Priority 1].
Techniques:
Rationale: PDF and other page rendering technologies often create pages that cannot be viewed or navigated using standard web access tools.
Techniques:
Rationale: The accessibility of objects with their own interface is independent of the accessibility of the user agent. Accessibility must therefore be built into the objects or an alternative must be provided..
Techniques:
Rationale: Many users can not run scripts or applets at all. The "fail gracefully" provisions would cover this situation. However, some users who can, but rely on assistive technology such as screen readers or special input devices may not be able to receive the information, or activate the functions that the content provides.
Techniques:
Rationale: Some pages will be unable to fail gracefully at this time either because the visual components are too complex, or because assistive technologies or user agents (browsers) are lacking a specific feature.
Known instances when a text-only page will be needed (not a definitive list):
Techniques: