Section 508 Checkpoints

§ 1194.22 Web-based intranet and internet information and applications.

• (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
  • All meaningful images should have alt text. You can quickly check whether images on your page have alt text using the WAT Images tool
  • All complex images (such as a graph or cartoon) should have a longdesc attribute, containing a link to a description/interpretation of the image. This is most useful placed at the bottom of the same page using an anchor (e.g. <img src="refererence_graph" longdesc="#graphexplained"/>
• (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
  • This means captioning. See Danielle's Camtasia Class page for links to tutorials on creating captioned Camtasia videos.
• (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
  • Although you may use color in your pages, you shouldn't use it alone for emphasis, or refer to parts of your instructional page by color alone (e.g. "that red box"). Use labels instead.
• (d) Documents shall be organized so they are readable without requiring an associated style sheet.
  • Your page should be readable in a top-to-bottom linear fashion (this is how screen-readers do it). Test to make sure your page makes sense without the style sheet by turning it off in your browser.
• (e) Redundant text links shall be provided for each active region of a server-side image map.
  • N/A
• (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.
  • N/A
• (g) Row and column headers shall be identified for data tables.
  • A data table is a table used to present tabular data. Your table header row or header column cells are properly marked up if they use <th> tags instead of <td> tags. You can assign a header row in Dreamweaver using the Table Properties panel or in Contribute using the Table Properties dialog.
  • If your table is just for layout, disregard.
• (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.
  • Generally not an issue unless you unusually complex data. See the WebAim tutorial on how to use the id and headers attributes to communicate the the significance of cell content more precisely
• (i) Frames shall be titled with text that facilitates frame identification and navigation.
  • The Library doesn't use frames in its pages as a rule. If you are using an iframe in a bit of code (like the Wordcat search widget), the iframe element should contain a title attribute.
• (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
  • No dancing gifs or flashing text (but you know this already!)
• (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.
  • N/A for librarian pages
• (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.
  • If you embed a script or widget in your page (YouTube, Camtasia, and Meebo are good examples), a screen reader should be able to interpret what it is. You should also be able to interact with it using the keyboard. If youa re not sure if you're embedded widget or movie is accessible, please ask.
• (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).
  • Not to worry --Most scripted widgets and movies contain links to the required application (usually, Flash) which will appear if the application is missing.
  • BUT. . .any page that contains links to PDF files should contain a link to the Adobe Reader (Dreamweaver users, see the Code Library; Contribute users . . .
• (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.
  • At a mimum, all form inputs (text boxes, checkboxes, dropdown selects, etc) require labels. See WebAim Create Accessible Forms tutorial or contact Elizabeth Altman for assistance.
• (o) A method shall be provided that permits users to skip repetitive navigation links.
  • This is already built into the templates.
• (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
  • N/A for librarian pages.