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. All Section 508 Standards are included in Priority 1. These guidelines represent the highest priority of accessibility features that must be addressed in web page design.

Go to Priority 1 Item 1
Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols and logos), image map regions, animations (e.g., animated GIF's), applets and other programmatic objects, graphical buttons, audio, video, itc.. [W3C WCAG 1.0, 1.1] [Sec.508 1194.22(a)]

Go to Priority 1 Item 2
Ensure that all information conveyed with color is also available without color, for example from context or markup. [W3C WCAG 1.0, 2.1] [Sec.508 1194.22(c)]

Go to Priority 1 Item 3
Use style sheets to control presentation while ensuring that all content is accessible in user agents that do onot support or do not fully support style sheets. [W3C WCAG 1.0, 6.1] [Sec.508 1194.22(d)]

Go to Priority 1 Item 4
Avoid causing the screen to flicker. [W3C WCAG 1.0, 7.1] [Sec.508 1194.22(j)]

Go to Priority 1 Item 5
Client side image maps should be provided instead of server side image maps. If you must use server-side image maps, provide redundant text links for each link on the image map. [W3C WCAG 1.0, 1.2 and WCAG 1.0, 1.5] [Sec.508 1194.22(e) and 1194.22(f)]

Go to Priority 1 Item 6
Use of frames is discouraged. If you must use frames, title each frame to facilitate frame identification and navigation. [W3C WCAG 1.0, 12.1] [Sec.508 1194.22(i)]

Go to Priority 1 Item 7
Ensure that foreground content is easily distinguishable from the background, particularly when viewed by someone with color deficits. [W3C WCAG 1.0, 2.2]

Go to Priority 1 Item 8
Clearly identify the target of each link. [W3C WCAG 1.0, 13.1]

Go to Priority 1 Item 9
Use markup according to specification. For example, use header elements to convey document structure. Mark up lists and list items properly. Mark up quotations. Do not use quotation markup for formatting effects such as indentation [W3C WCAG 1.0, 3.5; WCAG 1.0, 3.6; WCAG 1.0, 3.7]

Go to Priority 1 Item 10
Use markup to identify the primary natural language of a document and any changes in its natural language, (including those in text equivalents, captions, etc. [W3C WCAG 1.0, 4.1 and WCAG 1.0, 4.3]

Go to Priority 1 Item 11
Make scripts and applets that allow users to interpret or access page content, or any other element that has its own interface, compatible with assistive technologies, and ensure that event handlers are input device-independent. [W3C WCAG 1.0, 6.4; WCAG 1.0, 8.1; WCAG 1.0, 9.2] [Sec.508 1194.22(m)]

Go to Priority 1 Item 12
Ensure that all content is accessible when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. (See also P1, #1, #11, #19) [W3C WCAG 1.0, 6.3]

Go to Priority 1 Item 13
For data tables, identify row and column headers. Use markup to associate data cells with header cells for data tables that have two or more logical levels of row or column headers [W3C WCAG 1.0, 5.1 and WCAG 1.0, 5.2] [Sec.508 1194.22(g) and 1194.22(h)]

Go to Priority 1 Item 14
Provide summaries for data tables. If a table is used only for layout, provide an empty summary attribute (e.g., summary=" ").[W3C WCAG 1.0, 5.5]

Go to Priority 1 Item 15
Use markup to associate all form controls with their labels. [W3C WCAG 1.0, 10.2 and WCAG 1.0, 12.4] [Sec.508 1194.22(n)]

Go to Priority 1 Item 16
For any time-based multi-media presentation (e.g., movie or animation) synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation. [W3C WCAG 1.0, 1.4] [Sec.508 1194.22(b)]

Go to Priority 1 Item 17
When a timed response is required, the user shall be alerted and given sufficient opportunity to indicate more time is required. [Sec.508 1194.22(p)]

Go to Priority 1 Item 18
Provide a method that permits users to skip lists of links repeated on every page in a site, such as navigation links. [W3C WCAG 1.0, 13.6] [Sec.508 1194.22(o)]

Go to Priority 1 Item 19
If you cannot create an accessible page, provide a link to an alternative page that is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page. [W3C WCAG 1.0, 11.4] [Sec.508 1194.22(k) and 1194.22(l)]