IBHE Web Accessibility Reporting Requirements

Revised (6/27/2007)

These requirements are being developed as apart of the activities of the IBHE Web Accessibility Consortium

Effective Dates

Reporting period starting January 1st 2008 and all subsequent reporting periods, until superseded by other requirements. Plans for 2008 should be included in January 2008 report on 2007 web accessibility progress.

Which campus committees address web accessibility issues and which of the following canpus units particpate in these committees?

• Academic Officer representative (i.e. Provost, Vice President, Chancellor)
• Human Resources
• Public Affairs or Marketing
• Foundation/Marketing
• Disability resources
• Instructional technology
• Library
• Information technology
• Faculty representative
• Student affairs
• Registrar, Admissions and Records
• Procurement/Purchasing
• Athletics
• Other units, please list the units who participate

Summarize Committee Activities related to Web Accessibility

• How do you communicate your web accessibility practices to faculty, staff, students and the general public?
• How often does the committee discuss web accessibility issues on campus?
• How does the committee promote accessible web design on campus to web developers and what training resources are available to web developers to learn about accessible design practices?
• How does the institution or the committee decide on which web resources to make accessible?
• How are students involved in identifying web accessibility issues on campus?
• How is web accessibility addressed in your campus strategic plan?
• What are your web accessibility procurement requirements?
• Does your campus participate in the IBHE Web Accessibility Consortium?
• Do you include web accessibility as part of your disability awareness day on your campus?

Provide Information on Web Accessibility Improvements and Plans for your Institutions

• Define your accessibility requirements.
• List the evaluation tools and procedures you use to evaluate accessibility of web resources at your institution.
• List the web sites that were brought into compliance to your web accessibility requirements during the past year.
• List the web sites you plan to bring into compliance to your web accessibility requirements during the next year.

Web Application Accessibility

Enterprise level web applications must be accessible to people with disabilities and are usually purchased resources so the accessibility is not under the direct control of the institution. Web applications include tools for course management, web mail, campus portals and content management systems. Institutions must work with companies or open source projects to verify and improve the accessibility of web applications. The identification of technical staff who can understand the technical details of accessibility is important in creating statewide networks of institutions to work with companies and open source developers to improve accessibility.

1. List the web applications your institution uses in each of the following categories:
   • Course management systems (i.e. Blackboard, Moodle, Sakai, Angel, Desire2Learn)
   • Campus portal system (i.e. uPortal)
   • Web mail (i.e. Mirapoint, Google Mail,…)
2. List the activities and the progress of your campus during the past year to improve the accessibility of these web applications.
3. List your planned activities to improve the accessibility of these web applications during the next year. NOTE: The IBHE Web Accessibility Consortium currently supports many multi-institutional efforts on improving the accessibility of web applications./li>