Web designers may begin to hear about accessible web design and a law referred to as 508. This page is for University of Oregon web designers and is intended to help clarify some of the issues.
What is it?
The legislation referred to as "Section 508" is actually an amendment to the Workforce Rehabilitation Act of 1973. The amendment was signed into law by President Clinton on August 7, 1998. Section 508 requires that electronic and information technology that is developed or purchased by the Federal Government is accessible by people with disabilities.
To whom does it apply?
It applies to the federal government (with some military and intelligence exceptions.) There is some question as to whether it applies to states. Governor Kitzhaber has signed a letter stating that Oregon will comply with 508.To what does it apply?
- Web-based Intranet and Internet Information and Applications <<This page is concerned with this item.
- Software Applications and Operating Systems
- Telecommunications Products
- Video and Multimedia Products
- Self Contained, Closed Products Desktop and Portable Computers
Is there a deadline?
Section 508 will have a rolling implementation that begins on June 21, 2001. A rolling implementation means that its standards are to take effect on the next redesign of a web site.Whether or not this applies to the university, it is the most concrete specification for (among other things) accessible web design. Access to university documents for people with disabilities is covered under more than one federal law. In the absence of any other web accessibility specifications, the ones contained in 508 are the very least that we should apply to university web pages.
This summary of 508 web-design standards was taken from the U.S. government document entitled Final Standards.
(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
(d) Documents shall be organized so they are readable without requiring an associated style sheet.
(e) Redundant text links shall be provided for each active region of a server-side image map.
(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.
(g) Row and column headers shall be identified for data tables.
(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.
(i) Frames shall be titled with text that facilitates frame identification and navigation.
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
(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.
(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).
(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.
(o) A method shall be provided that permits users to skip repetitive navigation links.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
Support
University of Oregon web designers may contact James Bailey at 6-1076 or by e-mail at jbailey@darkwing.uoregon.edu.
Two official government sites can be found at www.section508.gov/ and http://www.access-board.gov/news/508-final.htm.
Some useful coding examples may be found at http://www.diboc.com/wrac.cfm.
Macromedia has plug-ins and more at http://www.macromedia.com/macromedia/accessibility/.
Another private page with useful information: http://www.jimthatcher.com/webcourse1.htm.
University of Oregon Home Page
Comment on this
Page
This site is maintained by James Bailey, the university's Adaptive Technology
Access Adviser.
