Compliance Guidelines Used

• Provided equivalent alternatives to auditory and visual content.
• Provided a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
• Provided redundant text links for each active region of a server-side image map.
• Until user agents can automatically read aloud the text equivalent of a visual track, provided an auditory description of the important information of the visual track of a multimedia presentation.
• For any time-based multimedia presentation (e.g., a movie or animation), synchronized equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.
• Ensured that all information conveyed with color is also available without color, for example from context or markup.
• Clearly identified changes in the natural language of a document's text and any text equivalents (e.g., captions).
• Created tables that transform gracefully.
• For data tables, identified row and column headers.
• For data tables that have two or more logical levels of row or column headers, used markup to associate data cells and header cells.
• Ensured that pages featuring new technologies transform gracefully.
• Organized documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.
• Ensured that equivalents for dynamic content are updated when the dynamic content changes.
• Ensured that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provided equivalent information on an alternative accessible page.
• Until user agents allow users to control flickering, avoided causing the screen to flicker.
• Made programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies.
• Provided client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
• If, after best efforts, an accessible page was not possible, provided a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.
• Titled each frame to facilitate frame identification and navigation.
• Used the clearest and simplest language appropriate for the site's content.

Insuring Complianceinsure

The Center for Applied Special Technology (CAST) created a tool called Bobby, which is a Web-based program that helps designers recognize components of a site that may make the site difficult to access. Bobby identifies accessibility problems on Web pages and suggested means of altering those pages to be more accessible. We did extensive testing using this tool to help locate and update problem areas on the site.

Remaining Problems

Although we have attempted to be diligent in providing equal access to TusCOEMA's website, we are aware that some areas may need additional improvements. Limitations of the Bobby software and the large size of the TusCoEMA's site may have allowed pages with limited accessibility to remain and your assistance is greatly appreciated in alerting us so that we may update those sections. If you have difficulty accessing any information on this site, please contact our Webmaster.

Viewing PDF documents requires Adobe Reader.

FREE Adobe Acrobat Reader DownloadFor Persons with accessibility difficulties: