|
|
|
Cybertelecom
Federal Internet Law & Policy
An Educational Project
|
|
Accessibility: Sec. 508 |
Prior to 1998, Section 508 of the Rehabilitation Act provided voluntary guidance regarding the accessibility of federal IT. [Access Board Questions and Answers para. 5] As with other guidance in the voluntary category, its effectiveness was somewhat restrained.
That changed. The Workforce Investment Act of 1998 contained an amendment to Section 508 that transformed it from voluntary to obligatory. [Fed. Reg.] [Thatcher] That got attention. Now Section 508 requires federal agencies and the Post Office to "develop, procure, maintain, or use electronic and information technology" that is "accessible to people with disabilities, unless it would pose an undue burden." [36 CFR s 1194.1] [FAQ Q. 5] [Fed. Reg.] Pretty much anything the government uses must be accessible. Also, anything anyone wants to build for or sell to the government must be accessible. In addition, federally employees whose job function requires access to information technology must be provided with appropriate technology to facilitate accessibility. [29 USC Sec. 794d] [36 CFR Part 1194] [ See also ADA Title I] If an agency thinks that accessibility might in fact cause an undue burden, that agency faces a mound of paperwork in which it must justify its conclusion and also provide the information in question via alternative means.[36 CFR s 1194.2] [Fed.Reg.] Section 508 is designed for the benefit of federal employees and members of the public seeking to federal information. Given the vast number of IT companies bidding for and fulfilling government contracts, and given the impact that government procurement can have on the market, this is no small obligation.
There are a few exceptions to Section 508. [FAQ Q. 12] It occurred to Congress that things that go boom really don't need to be made accessible to the disabled. If the military wants go built a million dollar missile, whose purpose it is to turn-on once, fly across the sky, and then be obliterated into very tiny pieces, there is probably no need to provide a braille interface with that missile. Thus, pursuant to Section 508, the following systems need not be made accessible: military command, encryption, weapons, and intelligence. [36 CFR s 1194.3.] [Sec. 508 Summary Subpart A] [Fed.Reg.] [29 USC Sec. 794d]
In addition, when accessibility would require a "fundamental alternation" of the product, turning it into something that it was not, this too is an exception. The example here is a pocket-pager. Adding a large display to a pocket pager in order to make the screen readable to those with visual disabilities would mean that it is no longer a "pocket pager." This is a fundamental alteration and it is not required. [36 CFR s 1194.3(e)] [Fed.Reg. Subpart A]
A few things that Section 508 does not cover. Section 508 does not cover back office equipment - in other words, equipment in inaccessible locations that is generally used only be service maintenance staff. [36 CFR s 1194.3(f)] [Fed.Reg. Subpart A] Section 508 does not cover the recipients of federal funds. [FAQ Q. 12] [Thatcher Sec. 1.1] [See Education] Section 508 also does not cover incidental IT that a contractor may use in order to fulfill a government contract. Saying it a different way, if a contractor is hired to build a federal website, then the website must comply with Section 508 but the equipment that the contractor uses to build the website need not. [36 CFR s 1194.3(b)] [Fed.Reg. Subpart A] Finally, Section 508 does not require superfluous accessibility. Not every desktop computer needs a braille reader; however, every desktop computer should be compatible with a braille reader should one need to be installed. [36 CFR s 1194.3(c)] [DOJ Summary]
Section 508 covers all IT: photocopy machines, desktop computers, Internet resources, and more. Given the scope of this book, we will look only at the guidance for Internet resources (in other words, do not forget that the other stuff is out there).
As with all laws, the law was a broad stroke description of policy that some federal agency would be left to interpret and implement. The task of implementation was left to the Architectural and Transportation Barriers Compliance Board (a.k.a. Access Board) and the rules that they created can be found in title 36 of the Code of Federal Regulation, Part 1194. The rules that the Access Board developed paralleled close to, although not exactly, the work of the World Wide Web Consortiums Web Accessibility Initiative. [36 CFR § 1194.22 (note)] [Fed.Reg. Subpart B] [Sec. 508 Summary Subpart B] [Thatcher Sec. 1.3] Of course, this creates a peculiar scenario where Internet resources could be judged to be accessible by one set of standards but not accessible by another. The creation of inconsistent standards between bodies did not necessarily please everyone.
Nevertheless, tracking the standards of the W3C WAI, the Access-Board in its final rule indicated that a website would need to comply with the following 13 items in order to be considered accessible:
- A test equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
- Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
- Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
- Documents shall be organized so they are readable without requiring an associated style sheet.
- Redundant text links shall be provided for each active region of a server-side image map.
- 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.
- Row and column headers shall be identified for data tables.
- Markup shall be used to associate data cells and headers cells for data tables that have two or more logical levels of row or column headers.
- Frames shall be titled with test that facilitates frame identification and navigation.
- Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
- 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.
- When pages utilize scripting languages to display context, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.
- 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).
- When electronic forms are designed to be completed online, 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 clues.
- A method shall be provided that permits users to skip repetitive navigation links.
- When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
[36 CFR § 1194.22]. Unlike the ADA , Section 508 is not enforceable by the Department of Justice. Instead, aggrieved parties may complain directly the federal agency in question. Aggrieved parties also have the right to initiate litigation. [DOJ Summary(citing 29 USC s 794d(f))].
Section 508 of the Workforce Rehabilitation Act of 1973, as amended |
. |
| "On December 21, 2000, the Access Board released final standards for accessibility of federal technology. "These standards, the first of their kind in the Federal sector, cover various means of disseminating information, including computers, software, and electronic office equipment. They provide criteria that spell out what makes these products accessible to people with disabilities, including those with vision, hearing, and mobility impairments. The Board developed these standards under section 508 of the Rehabilitation Act as amended by Congress in 1998. The law applies to all Federal agencies when they develop, procure, maintain, or use such technology. Federal agencies must ensure that this technology is accessible to employees and members of the public with disabilities to the extent it does not pose an "undue burden." The law directed the Board to develop access standards that are to become part of the Federal government's procurement regulations. The scope of section 508 and the Board's standards are limited to the Federal sector.
"The new standards provide technical criteria specific to various types of technologies and performance-based requirements, which focus on the functional capabilities of covered technologies. Specific criteria cover software applications and operating systems; web-based information or applications; telecommunications functions; video or multi-media products; self contained, closed products such as information kiosks and transaction machines, and computers. Also covered is compatibility with adaptive equipment people with disabilities commonly use for information and communication access.
"The standards are based on recommendations from an advisory committee the Board established for this purpose. The Electronic and Information Technology Access Advisory Committee was composed of 27 members representing industry, various disability organizations, and other groups with an interest in the issues to be addressed. The Board published the standards in proposed form on March 31, 2000 and made them available for public comment for 60 days. Over 100 individuals and organizations submitted comments on the standards. Comments were submitted by Federal agencies, representatives of the information technology industry, disability groups, and persons with disabilities. The Board finalized the standards according to its review and analysis of these comments.
"The final standards, which will become part of the Federal procurement regulations, will help Federal agencies determine whether or not a technology product or system is accessible. Section 508 uses the Federal procurement process to ensure that technology acquired by the Federal government is accessible. The law also sets up an administrative complaint process which becomes effective 6 months from publication of the Board's standards." Access Board 508 Final Website December 20, 2000
|
|
US Dept Education: Requirements for Accessible Electronic and Information Technology Design (Feb 1, 2001)
A WEB ACCESSIBILITY EVALUATION AND REPAIR TOOL WITH APPLICATION TO SECTION 508 STANDARDS
WEBAim Section 508 Accessibility Checklist
Government Computer News 508 Center
Law
Papers
- Summary of Section 508 Standards section508.gov
- Access Board
- JimThatcher.com Web Accessibility for Section 508
Section 508 Web Standards and WCAG Priority 1 Checkpoints A Side-by-side Comparison
- USDOJ, Sec. 508 Executive Summary & Recommendations.
- John J. Pavlick, Jr. & Rebecca Pearson, Implementing the New 508 Accessibility Standards for the Disabled, 36 Spr. Procurement Law. 1 (2001).
- Latresa McLawhorn, Leveling the Accessibility Playing Field: Section 508 of the Rehabilitation Act, 3 N.C. J.L. & Tech. 63 (2001).
- Paul Taylor, The Americans with Disabilities Act and the Internet, 7 B.U. J. Sci. & Tech. L. 26 (Winter 2001) (includes discussion of Sec. 508)
- ITAA Quick and Easy Accessibility for Section 508? . Finding Low Cost Methods for 508 Accessibility. Presenter - Dr. Gregg C. Vanderheiden, Director, Trace Research & Development Center with Rex Lint, Consultant Specializing in Technology Accessibility & Chairman of ITAA's Section 508 Task Group as host Presentation pdf | Real Audio | Transcript | Oct 17 2001
- ITAA Section 508 Webcast: Exemptions, Exceptions, and the Responsibilities of Agencies and Vendors Mr. Doug Wakefield of The Access Board, with host Rex Lint, IT Accessibility Consultant & Chairman of ITAA's Section 508 Task Group Presentation | Real Audio | Transcript | Nov 14 2001
Links
News
- DHS creates 508 program, FCW 10/12/2004
- Site Accessibility for the Disabled May Be Required, IDG.net (Oct. 16, 2002).
- FAR amendments irk industry, FCW 5/2/01
- GSA releases FAR rules for Section 508, GCN 5/2/01
- Making Uncle Sam Accessible--and Accountable, BusinessWeek Online (June 13, 2001).
- Final rules governing IT accessibility Issued, GovExec 5/2/01
- Standards Body Pushes Accessibility Online, CNET News.com (Sept. 17, 2001).
- Report Urges Congress to Make Legislative Branch Compliant with Section 508, Wash Tech 11/27/01
- Colleges Focus on Making Web Sites Work for People With Disabilities, Chronicle for Higher Education Jan 26, 2001 (concluding that Sec. 508 applies to state educational institutions that receive funds under the Assistive Technology Act - however others believe this article is inaccurate)
- Advocates Happy With Accessibility Rules Dec 28 suntimes
- Fed Opens Web to Disabled Dec 28 wired
- Disabled gain access to gov't sites Dec 28 zdnet
- Fed Sets Accessibility Standards For Web Sites Dec 22 techserver
- Govt. sites subject to accessibility rules Dec 22 usatoday
- July 18, 2000 -- President Clinton signed a bill (HR 4425, Section 2405) that defers the effective date for enforcement of Section 508. Section 508 requires that Federal agencies' electronic and information technology is accessible to people with disabilities, including employees and members of the public. As originally enacted in 1998, the provisions of Section 508 relating to enforcement were to go into effect on August 7, 2000. The new amendment changes the effective date to six months after the Access Board publishes its final standards under section508
- Feds might get short reprieve on Section 508 GCN 6/12
- Trade Group Reacts To Govt's Site Accessibility Rules WashTech 5/31
- Janet Reno gives keynote address on Sec 508 at FOSE Speech should be uploaded to the DOJ website
- Feds Publish Web Access Rules, Computerworld (Dec. 21, 2000).
- Feds Open Web to Disabled, WiredNews (Dec. 21,2000).
- U.S. won't release new Web site regs for review yet, Freedom Forum Feb 2000
- Congress Wakes Up to the Internet, Boardwatch (October 1998)
|