Web Accessibility University Marketing and Communications Web Resources > Web Accessibility > MTU Web Accessibility Guidelines IV. MTU Web Accessibility Guidelines Draft - June 21, 2002 Web Policy Committee The Americans with Disabilities Act (ADA) requires that institutions provide "reasonable accommodations" to clients and users with disabilities. It goes beyond prohibiting discrimination; it ensures inclusion for everyone in education, work-life, and services in their communities. MTU is committed to making all our campus activities accessible to users, including those who may be disabled, or differently abled. Any questions about the ADA may be directed to the MTU Affirmative Action Office. Web publishers must be aware of the accessibility needs of those getting information about MTU from our Web site. Examples of those with special needs are people with visual disabilities who will benefit from labels for graphics, text descriptions for videos, and support for screen reader compatibility. Web accessibility improvements often have carry-over benefits for all users. When developing pages, Web publishers should refer to the Michigan Tech Web Accessibility standards for guidance in creating content that is accessible to the widest possible audience. 1. General Guidelines 1.1 University Help Desk Support for Web Accessibility Web creators should contact the following for help desk support regarding MTU Web Accessibility Guidelines: Web and computing support personnel in their own departments. External resources available online throughout the internet. University Marketing and Communications. The University maintains basic support and documentation regarding web page accessibility, managed by University Marketing and Communications. More information may be found at www.admin.mtu.edu/urel/webresources/. This site includes recommended accessibility checkpoints, examples, tips, and links to external resources. 1.2 Web Pages Recommended for Accessibility Checking It is strongly recommended that the Recommended Checkpoints be applied to the following pages: All new or substantially revised official Departmental pages All existing official Departmental pages containing core information The Departments are free to identify which of their web pages contain core information. Examples would be web pages containing information about academic programs, advising, course work, registration, forms, admission, student services, and policies. Accessibility standards may be relaxed somewhat for pages that are purely or mainly promotional. All Departments are REQUIRED to identify their main contact web page and to implement the following checkpoint standards for that page. 2. Recommended Checkpoints In 1998, Congress amended the Rehabilitation Act to require Federal agencies to make their electronic and information technology accessible to people with disabilities. Michigan Tech strongly encourages the implementation of the web checkpoints listed in subsection 1194.22 of the Federal Rehabilitation Act Section 508. They are included below, with links to explanations, examples, and WCAG equivalent checkpoints. Section 508 Web Checkpoints Subsection 1194.22 of the Federal Rehabilitation Act Section 508 Web-based Intranet and Internet Information and Applications (1194.22) 1194.22 (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). 1194.22 (a) | WCAG Priority 1: 1.1 1194.22 (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. 1194.22 (b) | WCAG Priority 1: 1.4 1194.22 (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. 1194.22 (c) | WCAG Priority 1: 2.1 1194.22 (d) Documents shall be organized so they are readable without requiring an associated style sheet. 1194.22 (d) | WCAG Priority 1: 6.1 1194.22 (e) Redundant text links shall be provided for each active region of a server-side image map. 1194.22 (e) | WCAG Priority 1: 1.2 1194.22 (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. 1194.22 (f) | WCAG Priority 1: 9.1 1194.22 (g) Row and column headers shall be identified for data tables. 1194.22 (g) | WCAG Priority 1: 5.1 1194.22 (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. 1194.22 (h) | WCAG Priority 1: 5.2 1194.22 (i) Frames shall be titled with text that facilitates frame identification and navigation. 1194.22 (i) | WCAG Priority 1: 12.1 1194.22 (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. 1194.22 (j) | WCAG Priority 1: 7.1 1194.22 (k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of these standards, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. 1194.22 (k) | WCAG Priority 1: 11.4 1194.22 (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. 1194.22 (l) | WCAG Priority 1: 6.3 | WCAG Priority 2: 6.4 | WCAG Priority 2: 8.1 | WCAG Priority 2: 9.3 1194.22 (m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with ?1194.21(a) through (l). 1194.22 (m) | WCAG Priority 1: 6.3 | WCAG Priority 2: 6.4 | WCAG Priority 2: 8.1 1194.22 (n) When electronic forms are designed to be completed on-line, the form shall 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. 1194.22 (n) | WCAG Priority 2: 10.2 | WCAG Priority 2: 12.4 | WCAG Priority 2: 9.3 1194.22 (o) A method shall be provided that permits users to skip repetitive navigation links. 1194.22 (o) | WCAG Priority 3: 13.5 | WCAG Priority 3: 13.6 1194.22 (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. 1194.22 (p) Next: V. Doing More