Accessibility
ATI Process Guide
First Year ATI Web Accessibility Project
Draft 2.0
This process guide combines the use of the HiSoftware tool with the manual check process to help campus departments improve the accessibility of their Web sites and to create the transition plan for full compliance.
Methodology
1. Select a set of sample sites to represent administrative public web site cross-section.
a. Sample web sites should be no less than 15 and not more than 100 sites.
b. The following is an example of some sample web sites:
- Campus main site
- Each college and school
- Disabled student services
- Random departments
- Divisions
- University portal
2. Submit list of “Sample Sites” to ATI Steering Sub-committee for review.
a. Members of ATI Steering Sub-committee:
- Bill Post
- Amir Dabirian
- Gilbert Gonzales
- Wayne Dick
- Kevin O’Brien
- Mary Cheng
3. ATI Steering Sub-committee will turn around the review to the campus within three business days.
4. Install HiSoftware and configure to use 508 standards to run against all “Sample Sites.”
5. Remediate each sample site to achieve a passing score of 80‰ or greater — exceptions to the attainment of the 80‰ must be documented and include exception rationale and a plan to provide equal and effective access.
6. Generate detail report using HiSoftware.
7. Select 20‰ of the “Sample Sites” and perform a manual check of the main home page (index page) of this smaller sample.
8. Remediate all manual checked pages to achieve 100‰ compliance — exceptions to the attainment of full compliance must be documented and include exception rationale and a plan to provide equal and effective access.
9. The Manual Checker application will verify step-by-step the manual check process and create an output.
10. Submit report to the Chancellor’s Office that includes the results of this project and a transition plan to improve web accessibility and reaching full compliance in accordance with established timelines.