WCAG 2.0 Priority Level AA
2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen.
Our color choices for textual content exceed requirements in brightness difference, color difference, and contrast.
3.1 When an appropriate markup language exists, use markup rather than images to convey information.
Images are used for decoration, and to represent people, events, and places.
3.2 Create documents that validate to published formal grammars.
Our HTML validates without errors.
3.3 Use style sheets to control layout and presentation.
Stylesheets are used for layout and presentation.
3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values.
Our textual content uses scalable font sizes that can be changed using browser settings.
3.5 Use header elements to convey document structure and use them according to specification.
Header (H) tags are used to create an outline of page content.
3.6 Mark up lists and list items properly.
List HTML validates without error.
3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation.
Quotation tags are not used for formatting.
5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version).
Tables are not used for layout.
5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting.
Tables are not used for layout.
6.4 For scripts and applets, ensure that event handlers are input device-independent.
No APPLETs or EMBEDs are used. When SCRIPTs are used output is not input dependent. When OBJECT is used to present video, the video both pointer and keyboard controls.
6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page.
We do not use SCRIPTing or DHTML to change any informational content.
7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off).
Animation, BLINK, MARQUEE are not used.
7.3 Until user agents allow users to freeze moving content, avoid movement in pages.
Animation, BLINK, MARQUEE are not used.
7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.
We do not use auto-refreshing pages.
7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects.
Redirects, if used, are performed at the server.
8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies.
No APPLETs or EMBEDs are used. When SCRIPTs are used output is not input dependent. When OBJECT is used to present video, the video both pointer and keyboard controls.
9.2 Ensure that any element that has its own interface can be operated in a device-independent manner.
We use the standard HTML elements.
9.3 For scripts, specify logical event handlers rather than device-dependent event handlers.
When SCRIPTs are used output is not input dependent.
10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user.
We do not use pop-up windows.
10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned.
LABELs are used and properly positioned.
11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.
We do not use depreciated HTML tags. Our HTML validates without errors.
11.2 Avoid deprecated features of W3C technologies.
We do not use depreciated HTML tags. Our HTML validates without errors.
12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.
FRAMEs are not used.
12.3 Divide large blocks of information into more manageable groups where natural and appropriate.
All content is of a manageable length.
12.4 Associate labels explicitly with their controls.
LABELs are properly positioned.
13.1 Clearly identify the target of each link.
We do not use ambiguous or vague link text.
13.2 Provide metadata to add semantic information to pages and sites.
All pages have a title and all pages use the language META tag.
13.3 Provide information about the general layout of a site (e.g., a site map or table of contents).
We provide a site map.
13.4 Use navigation mechanisms in a consistent manner.
Menus and navigation are used consistently.
We welcome your suggestions and observations about accessibility. To send your comments, fill out our Accessibility Feedback Form.