Web Content Accessibility Guidelines 2.0 Is Available
Originally posted May 5, 2008
In general, web based 508 Accessibility requirements for software includes:
- Software Applications and Operating Systems - includes usability for people that are visually impaired, such as alternative keyboard navigation.
- Web-based Intranet and Internet Information and Applications – assures accessibility to web page graphics by the visually impaired using assistive technology such as screen readers and refreshable Braille displays.
- Videos or Multimedia Products - includes requirements for captioning of multimedia products such as training or informational multimedia productions. Captioning or video descriptors must be able to be turned on or off.
The Web Content Accessibility Guidelines 2.0 (WCAG 2.0) was published as a W3C Candidate Recommendation on 30 April 2008. The Candidate Recommendation stage means that there is broad consensus on the technical content, and W3C invites you to implement WCAG 2.0. Additional information in:
- WCAG 2.0 Candidate Recommendation Ready to Test Drive
- How WAI Develops Accessibility Guidelines through the W3C Process
- Overview of WCAG 2.0 Documents
Infinity Learning Solutions is adding closed captioning to DigitalChalk to help the hearing impaired. Is this enough? Does closed captioning really help the totally deaf who see English as a second language? I am exploring web based 508 requirements to determine the difference between guidelines and what is actually useful. There are helpful web sites for Accessibility Best Web Practices (Illinois Center for Information Technology Accessibility). I am especially interested in applying these practices to online learning. Any comments on this would be helpful.