Web Accessibility

Access Checklist

Expanded information on Accessibility Standard and Guideline Descriptions is available at
http://www.wright.edu/web/access/standards_508.html
http://www.wright.edu/web/access/guidelines.html

Check Number Standard/Guideline
  Standard (a)  (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
  Standard (b) (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
  Standard (c) (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
  Standard (d) (d) Documents shall be organized so they are readable without requiring an associated style sheet.
  Standard (e) (e) Redundant text links shall be provided for each active region of a server-side image map.
  Standard (f) (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.
  Standards (g) and (h) (g) Row and column headers shall be identified for data tables.
  Standards (g) and (h) (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.
  Standard (i) (i) Frames shall be titled with text that facilitates frame identification and navigation.
  Standard (j) (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
  Standard (k) (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.
  Standard (l) (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.
  Standard (m) (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).
  Standard (n) (n) When electronic forms are designed to be completed online, 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.
  Standard (o) (o) A method shall be provided that permits users to skip repetitive navigation links.
  Standard (p) (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
  Guideline 1  Create Web pages that are clear and simple, so they are more easily understood. 
  Guideline 2 Logically organize your page and use HTML to encode meaning rather than appearance -- use HTML tags for purpose they were created and use style sheets where appropriate. 
  Guideline 3  Provide clear and consistent navigation and links. 
  Guideline 4 Use color and background images judiciously.
  Guideline 5 Test your pages for accessibility.

3640 Colonel Glenn Highway - Dayton, Ohio - 45435
Copyright Information © 2005 | Accessibility Information
Last updated: Tue. Jan-10-06, 16:46
Please send comments to: webmaster@wright.edu
Wright State University