UT Tyler Web site Accessibility Policy

The University of Texas at Tyler
World Wide Web Design Accessibility Standards and Coding Guidelines
Designing Accessible Web Sites
This page is available for all persons who publish Web sites to the UT Tyler server.

The University of Texas at Tyler has adopted the Web Content Accessibility Guidelines 1.0 W3C Recommendation 5-May-1999 (WCAG) as the primary guideline to meet the objectives of the agency's Accessibility policy. These guidelines explain how to make Web content accessible to people with disabilities. The guidelines are intended for all Web content developers and site designers. The primary goal is to promote accessibility. However, following them will also make Web content more available to all users (e.g., browser, wireless phone, etc.). These guidelines do not discourage content developers from using images, video, etc., but rather explain how to make multimedia content more accessible to a wide audience.

UT Tyler Webmasters should try to achieve WCAG Conformance Level "AAA". The full checklist of Checkpoints for Web Content Accessibility Guidelines 1.0 can be found at http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/full-checklist.html

Universal Design

The purpose of this list is to provide a summary of the types of issues to consider when creating and designing accessible HTML pages:

Include a document type declaration (DOCTYPE) in your Web pages. This declares what version of HTML you are using in your documents, and assists the browser in rendering your pages correctly.
Avoid the use of HTML tags or extensions which are supported by only one browser.
Use headings, lists, and consistent structure.
Avoid the unnecessary use of icons, graphics and photographs. Note: This will also facilitate access to users of non-graphical browsers or slow Internet connections.
Check Web pages and images at different monitor resolutions, monitor sizes and color depth settings.
Use plain backgrounds and simple layouts to improve the readability of text.
Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen.
Maintain a standard page layout and navigation method throughout the Web site.
Do not abbreviate dates; for example, use December 1, 2000 rather than 12/1/00.
Ensure that dynamic content is accessible or provide an alternative presentation or page.
Until user agents allow users to freeze moving content, avoid movement in pages.
Test your Web pages with a variety of Web technologies; including ,but not limited to, graphical browsers with the images turned off, browsers with JavaScript disabled, a text based browser, using only your keyboard, and using assistive technology.

Text-Based Design

Avoid using side by side presentation of text, for example, columns and tables.
End all sentences, headers, list items, etc. with a period or other suitable punctuation.
All on line forms must be accessible!
Avoid/Limit the use of bitmap images of text, unless a textual alternative is also provided.
Consider using numbers instead of bullets to help the user to remember items.
Provide meaningful and descriptive text for hyperlinks, don't use short hand, e.g. "click here"; instead "Follow this link to our News Page". (Screen readers can search specifically for linked text, "click here" provides no indication of where the link will take them.) If documents are provided in a specialized format (e.g. PDF (Portable Document Format) , etc.) provide the equivalent text in HTML or plain text format.

Graphics and Images

Keep the number of colors in your pages to a minimum.
Minimize the file size and number of images you display on any one page.
Design your background image at the lowest color depth and resolution you can.
Ensure that text can always be clearly read at any location against the background.
Avoid/Limit using image maps.
Use the ALT tag attribute with image files to provide meaningful text for all images/pictures. Note: null (alt="") for simple images (e.g., a dot or bullet).

Audio/Visual Features

Provide text transcriptions of all video clips.
If possible include captions or text tracts with a description or sounds of the movie.
Provide descriptive passages about speakers and events being shown through video clips.
Give a written description of any critical information that is contained in audio files contained on your Web site.
If you link to an audio file, inform the user of the audio file format and file size in kilobytes.

Agency Accessibility Assessment Questions

Do Web pages have a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content)?
Do multimedia presentations have equivalent alternatives synchronized with the presentation?
Are Web pages designed so that all information conveyed with color is also available without color?
Are documents organized so they are readable without requiring an associated style sheet?
Are redundant text links provided for each active region of a server-side image map?
Are client-side image maps provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape?
Are row and column headers identified for data tables?
Do tables use markup to associate data cells and header cells for data tables that have two or more logical levels of row or column headers?
If frames are used, are they titled with text that facilitates frame identification and navigation?
Are Web pages designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz?
Is a text-only page, with equivalent information or functionality, provided to make a Web site accessible, when compliance cannot be accomplished in any other way? Is the content of the text-only page updated whenever the primary page changes?
If Web pages utilize scripting languages to display content, or to create interface elements, is the information provided by the script identified with functional text that can be read by assistive technology?
If a Web page requires that an applet, plug-in or other application be present on the client system to interpret page content, does the page provide a link to the plug-in or applet?
If electronic forms are designed to be completed on-line, does the form allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues?
Is a method provided that permits users to skip repetitive navigation links?
If a timed response is required, is the user alerted and given sufficient time to indicate more time is required?
Are Web pages designed to work on older versions of browsers?