Ex.3. Accessibility test of Peer's project 3 (25 points)

Check Syllabus for due date

post to assignment in Blackboard and review with peer

Requirements

• Use the W3C Web Accessibility Checklist to perform a review of 4 pages of your assigned peer's website (this HTML version has links to explain any checkpoints that you do not understand):
  • Home page (usually home.htm in root directory)
  • page containing form
  • page containing data table
  • page containing Flash movie
• Download accessibilitytest.doc (a Word version of W3C Accessibility Checklist with some added notes to help you make decisions.
  There are many items, but they only require a checkmark under "yes", "no" or "N/A" (not applicable).
  • Open each of the 4 pages.
  • Run the automated WAI test on the Web Developer's toolbar (cynthia says) to uncover obvious problems.
  • Cynthia says only checks elements that it can check automatically.
    There are qualitative checkpoints that have to be checked manually, which is what you are going to do.
  • Fill out a Word document form for each page you are testing.
    • accessibilitytestHome.doc
    • accessibilitytestForm.doc
    • accessibilitytestTable.doc
    • accessibilitytestFlash.doc
  • Upload the pages to the ex3 assignment in Blackboard -- name them
  • Print out copies to give feedback to your peer.
    

10 Quick Tips from W3C Web Accessibility Initiative (WAI)

Links to techniques documents provide implementation guidance that include explanations, strategies, and HTML markup examples.

1. Images & animations: Use alt attribute to describe function of each visual.
2. Image maps. Use client-side maps & text for hotspots.
3. Multimedia: caption and transcripts for audio, and descriptions of video.
4. Hypertext links. Use meaningful text not links such as "link" or "more" or "click here."
5. Page organization . Use Semantic structure: headings, lists, as they are intended. Layout and style with CSS stylesheets
6. Graphs & charts. Summarize or provide textual explanation.
7. Scripts, applets, & plug-ins. Provide alternative content in case active features are inaccessible or unsupported.
8. Frames. Use noframes element and meaningful titles.
9. Tables. Linearize, summarize data tables when necessary, but perform layout with CSS not layout tables. Use <th> tags to define column and row headers and give them ids.
10. Check your work. Validate. Use tools, checklists, and guidelines at http://www.w3.org/TR/WCAG