Web

Background

• CSU ATI's Web Accessibility page (timeline, 508 evaluation, workflow, reporting, FAQs, and tools)

Critical Dates

• June 1, 2010 - All department and vendor sites must be accessible.
• See coded memorandum AA-2009-19.
• Full timeline from the CSU ATI Web Accessibility page.

Charge

• Develop and plan for the accessible use of managed Web content universitywide (e.g. Charlotte, CSUMB.EDU) as specificed in EO 926.
• Monitor developments in assistive technology standards, tools, and systems as they related to our Web-enabled programs and services.
• Coordinate presentations and events to facilitate the exchange of knowledge about projects and planned developments as they relate to the Web and assistive technology services.

Draft Plan

• Establish membership of WAP team (April 2007)
• Develop Web presence for WAP, including FAQs, resources and tools (April 2007)
• Study, test & modify official CSUMB.EDU template on Charlotte for use by both visual and non-visual audiences (June - August 2007)
• Submit First Year Report to CSU ATI, based on the 20+ sites to initially evaluate (see WebPAT notes from January 2007) (May 2007)
• Discover non-Charlotte department websites that will need to be validated (June 2007)
• Make available AccRepair software for desktop (June 2007)
• Establish AccMonitor monthly reporting for all CSUMB virtual domains (TBA)
• Identify the biggest problem pages affecting most users, like Schedule of Classes, and develop strategies to fix them (TBA)
• Begin AccRepair training (TBA)
• Establish monthly walk-in labs for self-correction of pages (TBA)