Web Access for All Tool Kit
K-State's tool kit to assist University web developers
Accessibility defined
What accessibility means and how it affects web sites
Legal requirements
Describes K-State's federal and state legal obligations
Guidelines and standards
Links to federal, state, W3C guidelines and policies
Tools
Links to tools that can assist in achieving accessibility
Training and online tutorials
Links to classes and online training
Resources
Information about accessible emerging technologies and web-delivered curriculum
The following is a complete listing of the Section 508 standards covering web-based intranet and internet information and applications. For each item, the corresponding WCAG 1.0 checkpoint is provided. All WCAG 1.0 checkpoints are Priority 1 checkpoints (i.e., highest priority on a 3 point scale; violating them means your page will be totally inaccessible to one or more groups). Note that the last five items have no directly corresponding WCAG equivalent.
The The full text of Electronic and Information Technology Accessibility Standards. is available online.
(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). (WCAG 1.0 checkpoint 1.1 - Priority 1)
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. (WCAG 1.0 checkpoint 1.4 - Priority 1)
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. (WCAG 1.0 checkpoint 2.1 - Priority 1)
(d) Documents shall be organized so they are readable without requiring an associated style sheet. (WCAG 1.0 checkpoint 6.1 - Priority 1)
(e) Redundant text links shall be provided for each active region of a server-side image map. (WCAG 1.0 checkpoint 1.2 - Priority 1)
(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. (WCAG 1.0 checkpoint 9.1 - Priority 1)
(g) Row and column headers shall be identified for data tables. (WCAG 1.0 checkpoint 5.1 - Priority 1)
(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. (WCAG 1.0 checkpoint 5.2 - Priority 1)
(i) Frames shall be titled with text that facilitates frame identification and navigation. (WCAG 1.0 checkpoint 12.1 - Priority 1)
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. (WCAG 1.0 checkpoint 7.1 - Priority 1)
(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. (WCAG 1.0 checkpoint 11.4 - Priority 1)
(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. (No directly corresponding WCAG 1.0 checkpoint)
(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l). (No directly corresponding WCAG 1.0 checkpoint)
(n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. (No directly corresponding WCAG 1.0 checkpoint)
(o) A method shall be provided that permits users to skip repetitive navigation links. (No directly corresponding WCAG 1.0 checkpoint)
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. (No directly corresponding WCAG 1.0 checkpoint)