Section 508 Amendment to the Rehabilitation Act of 1973
From Wikipedia, the free encyclopedia
Section 508 of the Rehabilitation Act of 1973, as amended, was enacted by the Workforce Investment Act of 1998, Pub. L. No. 105-220, 112 Stat. 936 (Aug. 7, 1998), and is codified at .
Contents |
[edit] History
Section 508 was originally added as an amendment to The Rehabilitation Act of 1973, in 1986. The original section 508 dealt with electronic and information technologies, in recognition of the growth of this field.
In 1997, The Federal Electronic and Information Technology Accessibility and Compliance Act was proposed in the U.S. legislature to correct the shortcomings of the original section 508; the original Section 508 had turned out to be mostly ineffective, in part due to the lack of enforcement mechanisms. In the end, this Federal Electronic and Information Technology Accessibility and Compliance Act, with revisions, was enacted as the new Section 508 of the Rehabilitation Act of 1973, in 1998.
There is much misunderstanding about Section 508. Section 508 addresses legal compliance through the process of market research and purchasing and also has technical standards against which products can be evaluated to determine if they meet the technical compliance. Because technology can meet the legal provisions and be legally compliant (e.g., no such product exists at time of purchase) but may not meet the technical compliance (doesn't meet the Access Board's technical accessibility standards) users are often confused between these two issues. Add to that evaluation of compliance can be done only when reviewing the procurement process and documentation used when making a purchase or contracting for development, the changes in technologies and standards themselves, it requires a more detailed understanding of the law and technology than at first seems necessary.
There is nothing in section 508 that requires private Web sites to comply unless they are receiving federal funds or under contract with a federal agency. Commercial best practices include voluntary standards and guidelines as the World Wide Web Consortium's (W3C) Web Accessibility Initiative (WAI). Voluntary accessibility checkers (engines) as "Bobby" and AccVerify, refer to Section 508 guidelines but have difficulty in accurately testing content for accessibility.
[edit] The law
Section 508 requires that electronic and information technology developed, procured, used, or maintained by all agencies and departments of the Federal Government be accessible both to Federal employees with disabilities and to members of the public with disabilities, and that these two groups have equal use of such technologies as federal employees and members of the public that do not have disabilities.
[edit] Qualifications
- Federal agencies can be in legal compliance and still not meet the technical standards. Section 508 §1194.3 General exceptions describes exceptions for national security (e.g., most of the primary systems used by the National Security Agency (NSA), incidental items not procured as work products, individual requests for non-public access, fundamental alteration of a products key requirements, or maintenance access.
- In the case that implementation of such standards causes "undue hardship" to the Federal agency or department involved, such Federal agencies or departments are required to supply the data and information to covered disabled persons by alternative means that allow them to make use of such information and data.
[edit] Provisions
The original legislation mandated that the Architectural and Transportation Barriers Compliance Board, known as the Access Board, establish a draft for their Final Standards for accessibility for such electronic and information technologies in December 2001. The final standards were approved in April 2001 and became enforceable on June 25, 2001.
The latest information about these standards and about support available from the Access Board in implementing them, as well as, the results of surveys conducted to assess compliance is available from the Board's newsletter Access Currents. The Section 508 Standards, tools, and resources are available from The Center for Information Technology Accommodation (CITA), in the U.S. General Services Administration's Office of Government-wide Policy at section508.gov.
[edit] Summary of Section 508 technical standards
- Software Applications and Operating Systems: includes usability for people that are visually impaired, such as alternative keyboard navigation.
- Web-based Intranet and Internet Information and Applications: assures accessibility to web page graphics by the visually impaired using assistive technology such as screen readers and refreshable Braille displays. This is accomplished by using text labels and descriptors for graphics.
- Telecommunications Products: addresses accessibility for people who are deaf or hard of hearing. This includes technology compatibility with hearing aids, assistive listening devices, and TTYs.
- Videos or Multimedia Products: includes requirements for captioning of multimedia products such as training or informational multimedia productions. Captioning or video descriptors must be able to be turned on or off.
- Self Contained, Closed Products: products with embedded software, such as information kiosks, copiers, and fax machines, often cannot be used with assistive technology. This standard requires that access features be built into these systems.
- Desktop and Portable Computers: discusses accessibility related to mechanically operated controls such as keyboards and touch screens.
[edit] Frequently asked questions
- Is this part of the ADA?
- No, it is not. The Americans with Disabilities Act of 1990 is a different piece of legislation. Section 508 is an amendment to The Rehabilitation Act of 1973. Section 504 of the original Rehabilitation Act laid some of the groundwork for the ADA in the areas of rehabilitation, training and employment of disabled people.
- Is this related to, or the same as, the WWW Consortium's Web Content Accessibility Guidelines?
- They are not the same, but they are related. See [1] (This is Jim Thatcher's side by side comparison.) These WAI guidelines were considered in establishing the Access Board's Standards, as well as other resources. But the W3C's Web Content Accessibilies Guidelines are completely voluntary. On the other hand, the Section 508 Standards are enforceable as law and there are monetary penalties for non-compliance to the Access Board Standards. Under Section 508, covered parties alleging discrimination may institute civil suits based on alleged damages and, if successful, receive monetary awards.
- How do I make my websites 508 compliant?
- The portion of Section 508 which specifically relates to websites is under Sub-part B, 1194.22 section508.gov. In order for a website to comply with Section 508, it must adhere to the sixteen provisions listed therein. The Access Board website has an annotated reference Access-Board.gov with recommendations on how to implement these provisions, but it has not been updated since June 21st, 2001. On March 3rd, 2006, the Access Board stated Access-Board.gov that they intend to initiate an update to these standards during the summer.
- What's the difference between accessibility and usability?
- Although Section 508 addresses the accessibility of information technology by people with disabilities, it is no guarantee of practical usability by them. While usability is not mandated by federal regulations, it has become a best practice in government and industry. See TecAccess' article on "Five Factors of Usability" [2].
- Are there certain agencies exempt from this legislation?
- The law applies to all Federal agencies. There is some debate as to what legally defines an agency. Other Federal regulations and guidelines (e.g., Section 501 and Section 504 of the Rehabilitation Act) require equal access for individuals with disabilities. Therefore, Federal agencies are required, upon request, to provide information and data to individuals with disabilities through an alternative means of access that can be used by the individuals.
Also, please note that an agency can still be in legal compliance by meeting one of the § 1194.3 General exceptions. [3] (e.g., the NSA) However, systems which are critical to the direct fulfillment of military or intelligence missions do not include a system that is to be used for routine administrative and business applications (including payroll, finance, logistics, and personnel management applications) and therefore must be Section 508 compliant.
[edit] See also
[edit] References
[edit] External links
- United States Access Board the Federal Agency responsible for Section 508 technical standards
- Section 508 Checklist from WebAIM.org
- USPS AS-508-A, Section 508 Technical Reference Guide in HTML Format
- USPS AS-508-A, Section 508 Technical Reference Guide in PDF Format
- Federal Register December 2000 Section 508 Electronic and information technology accessibility standards
- Federal Register April 2005 Section 508 related Federal Acquisition Rules
- Voluntary Product Accessibility Template (VPAT) Guidelines for using the VPAT.