NOTE: Because your web browser does not support web standards, you will only be able to view the content in a linearized format. To use this site to it's fullest, you may wish to upgrade to a browser that supports web standards.

Resources, Validators and Testers

Web Accessibility Subcommittee (WAS)
- Main WAS Resource Page
- HTML Resources
- CSS Resources
- General Usability Resources

Lynx Viewer - This service allows web authors to see what their pages will look like (sort of) when viewed with Lynx, a text-mode web browser.

CSS Validator - W3C CSS Validation Service.

MarkUp Validation Service - A free service that checks documents like HTML and XHTML for conformance to W3C Recommendations and other standards.

Kansas Resources

Web Accessibility Subcommittee (WAS)
- Go to the WAS Homepage

Information Technology Advisory Board (ITAB)
- Go to the ITAB Homepage

Information Technology Executive Council (ITEC)
- Go to the ITEC Homepage

Web At Large

The World Wide Web Consortium (W3C)
- Go to the W3C Homepage

Web Accessibility Initiative (WAI)
- Go to the WAI Homepage

Web developers must satisfy this item. These guidelines represent more complex accessibility features that must be addressed in web page design. Generally, these items would be addressed after satisfying Priority 1 items.

Priority 2 Item 1
When an appropriate markup language exists, use markup rather than graphics to convey information. For example, use MathML to mark up mathematical equations instead of using graphics to represent symbols. [W3C WCAG 1.0, 3.1]

Priority 2 Item 2
Create pages that use the transitional or the strict document type declaration (e.g., <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> or <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">) and include the appropriate declaration as the first line of every HTML page. [W3C WCAG 1.0, 3.2]

Priority 2 Item 3
Use relative rather than absolute units of measure (e.g., for margins, font sizes, borders, etc.). [W3C WCAG 1.0, 3.4]

Priority 2 Item 4
Use navigation mechanisms in a consistent manner. [W3C WCAG 1.0, 13.4]

Priority 2 Item 5
Specify the expansion of each abbreviation or acronym in a document where it first occurs. Providing the expansion in the main body of the document also helps document usability. [W3C WCAG 1.0, 4.2]

Priority 2 Item 6
Inform the user before changing focus from the current window or before causing a "pop-up" or other new window to appear. (See also P1 #12) [W3C WCAG 1.0, 10.1]

Priority 2 Item 7
Provide multiple methods to explore sites that are more than two layers deep (e.g., add a site map or table of contents). [W3C WCAG 1.0, 13.3]

Priority 2 Item 8
Do not use tables for layout unless the table makes sense when linearized. [W3C WCAG 1.0, 5.3]

Priority 2 Item 9
Create a logical tab order through links, form controls, and objects. [W3C WCAG 1.0, 9.4]

Priority 2 Item 10
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. If necessary to re-direct a page and configuring the server is not possible, label the action and allow the user to invoke the link to the new page. [W3C WCAG 1.0, 7.5]