The Web Accessibility policy requires that web publishers be trained in designing and creating accessible web pages. Web publishers can utilize the following resources to attain this training:
- Self-paced classes via CD-ROM. Contact the O.T.I.S. webmaster for reservation and check out.
- Accessibility training hosted by UT Austin and scheduled through the Thompson Conference Center.
- Annual accessibility rally (AIR University). Hands-on training in a competitive environment hosted by UT Austin and Knowbility.
- The WebAIM – Web Accessibility In Mind web site. Extensive resource for self-paced learning about accessibility and staying current on techniques and issues. Check lists to verify web page accessibility are available for download.
Complete the following steps when creating new or maintaining existing web pages.
- Create and verify content for the web page.
- Create the web page based on a template (departmental or top tier) that incorporates the UT System look and feel.
- Apply techniques learned in accessibility training to ensure priority one* accessible web pages as defined by the W3C Web Content Accessibility Guidelines (WCAG).
- Test for Accessibility in accordance with WCAG.
- Test functionality by viewing through browser.
- Publish to production web site.
- Access the production site via a web browser and test the web page for functionality.
*The requirement is priority one but we would like to aim for priority two in order to provide a better experience for our customers.
Web publishers using DreamWeaver to produce web pages will begin testing for accessibility by using the Accessibility Suite for W3C/WCAG, V1.0.1 extension for DreamWeaver. The Accessibility Suite is available for download at the Macromedia Extensions web site.
Web publishers not using DreamWeaver to develop pages will use testing tools appropriate for their development environment.
Complete the following steps prior to publishing a document on the System Administration web site:
- View the web document using the following browsers
- Internet Explorer
- Netscape
- Optional: IBM Homepage Reader and JAWS
- View the web document in the following platforms:
- Windows
- Macintosh
- Test the web document using the following Accessibility Checking Tools
- DreamWeaver Accessibility Suite
- Bobby
- W3C Checklist of Checkpoints for Web Accessibility Guidelines. Keep a completed copy of this checklist for each page/site reviewed until a new change is made and the new documentation supersedes this.
- WebAIM tools
- Review the web page(s) for issues that the automated checking tools cannot identify (e.g., color contrast or text alternatives to items conveyed with color.)
- Test the web page(s) after publication to ensure it functions the same way on the production server as on the development server.
- Consider asking the O.T.I.S. Webmaster to review the web page(s).
Complete the following steps after major changes or redesign. These steps are intended for overall web site changes, as opposed to single page changes, and for high-profile, public-facing web pages.
- Test the web pages in an environment including people with disabilities.
- Perform a usability tests on the web pages. A more usable page is a more accessible page.
UT System Administration makes every effort to maintain an accessible website. The steps below apply when encountering an inaccessible web page:
- Web publisher or web user sends email to uts-feedback@utsystem.edu.
- OTIS willcontact the department web publisher and department head via email. The email message includes a deadline for making the web page accessible.
- OTIS shall remove from the production web site all web pages not accessible by their corresponding deadline.
- Upon specific request, the owner of the inaccessible web pageshall make the information available in an alternate format to any individual needing access to that web content.
