WCAG 2.0 Priority Level AAA
1.5 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.
Image maps are not used.
4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs.
Abbreviations and acronyms use proper markup.
4.3 Identify the primary natural language of a document.
Language is properly identified.
5.5 Provide summaries for tables.
We only use TABLEs for tabular, muti-dimensional lists and our TABLEs will always include summary, CAPTION, THEAD, and TBODY.
5.6 Provide abbreviations for header labels.
We only use one level of headers.
9.4 Create a logical tab order through links, form controls, and objects.
Tab order is maintained in read order and tabindex is not used.
9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.
Tab order is maintained in read order and accesskey is not used.
10.3 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.
We only use TABLEs for tabular, muti-dimensional lists and our TABLEs will always include summary, CAPTION, THEAD, and TBODY.
10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.
Place holders are used.
10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.
No adjacent links are used.
11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.)
Content type and language are properly identified.
13.10 Provide a means to skip over multi-line ASCII art.
ASCII art is not used.
13.5 Provide navigation bars to highlight and give access to the navigation mechanism.
Navigation bars are used.
13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group.
Related links are grouped and "skip" links are provided.
13.7 If search functions are provided, enable different types of searches for different skill levels and preferences.
Simple text search is provided.
13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc.
Our HTML validates without errors.
13.9 Provide information about document collections (i.e., documents comprising multiple pages.).
No pages comprise multiple pages.
14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.
Text is supplemented with graphics where appropriate.
14.3 Create a style of presentation that is consistent across pages.
Consistent styling is used on all pages.
We welcome your suggestions and observations about accessibility. To send your comments, fill out our Accessibility Feedback Form.