<h1>Web Accessibility</h1>
<h2>What Does It Mean?</h2>
Level Triple-A: Priority 3 Checkpoints
Quick links on this page:
[ Highlights ]
[ Images and image maps ]
[ Tables ]
[ Forms ]
[ Related topics ]
A Web content developer may address a Priority 3 checkpoint. Otherwise, one or more groups will find it
somewhat difficult to access information in the document. Satisfying this checkpoint will improve access
to Web documents.
(Source: "List of Checkpoints for Web Content Accessibility Guidelines 1.0")
Highlights:
- Specify the expansion of each abbreviation or acronym in a document where it first occurs. For example, use
<abbr title="Southern Illinois University Carbondale">SIUC</abbr>
for the first occurrence of the abbreviation "SIUC."
- Identify the primary natural language of a document. For example, the second line of this document is
<html lang="en">
- Create a logical tab order through links, form controls, and objects.
- Provide keyboard shortcuts to important links (including those in client-side image maps),
form controls, and groups of form controls.
- Until user agents (including assistive technologies) render adjacent links distinctly, include
non-link, printable characters (surrounded by spaces) between adjacent links.
- Provide information so that users may receive documents according to their preferences
(e.g., language, content type, etc.)
- Provide navigation bars to highlight and give access to the navigation mechanism.
- Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group.
- If search functions are provided, enable different types of searches for different skill levels and preferences.
- Place distinguishing information at the beginning of headings, paragraphs, lists, etc.
- Provide information about document collections (that is, documents comprising multiple pages).
- Provide a means to skip over multi-line ASCII art.
- Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.
- Create a style of presentation that is consistent across pages.
If you use images and image maps:
- Until user agents render text equivalents for client-side image map links, provide redundant
text links for each active region of a client-side image map.
If you use tables:
- Provide summaries for tables.
- Provide abbreviations for header labels.
- Until user agents (including assistive technologies) render side-by-side text correctly, provide a
linear text alternative (on the current page or some other) for all tables that lay out text
in parallel, word-wrapped columns.
If you use forms:
- Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.
Related topics
[ Workshop home ]
[ For Whom? ]
[ Why? ]
[ Overview ]
[ "Levels" ]
[ More information ]
[ Examples ]
[ ]
( Privacy Policy | Last saved August 17, 2004 )