Standards Make the Job Easier
- 16 specific technical standards for web accessibility
- General functional standards to apply when technical standards aren't clear
- No need to dumb down site - most standards have minimal effect on appearance
- Section 508 includes specific standards for software (not included in this class)
- Software on the web
- Possible, but difficult, to make pages acccessible
Priority 1 - "A web content developer must satisfy this checkpoint."
Priority 2 - "A web content developer should satisfy this checkpoint."
Priority 3 - "A web content developer may satisfy this checkpoint."
The final Section 508 rule includes so-called that require, for example, that there be a way for a person who is mobility impaired or blind to use your product or web site. So as a fall-back position, if the technical standards don't make requirements clear or if new technology is being employed, the functional requirements fill the gap.
The say your web site has to satisfy sixteen specific items for web accessibility. These are specific things you must do during web site development to ensure that a person who is mobility impaired or blind, for example, can use your site.
These standards, which are the basis of this course, do not require that you dumb down your site. Most sites can be made accessible without changing the visual experience at all.
For example, the standards say you must use alternative text for images and use client-side image maps instead of server-side maps. These are fairly simple and clear requirements. They are perhaps the most important, the most frequently ignored, and they have no impact on the way non-disabled users see or interact with the site.
As we have said, in addition to the web, the Section 508 final rule includes specific standards for software, hardware, and telecommunications equipment. The software requirements are relevant to the web today; Ajax is, in effect, creating software on the web. This course will not cover the .
There have been other efforts to establish guidelines for web accessibility, including those by and . All of them, including the 508 standards, have drawn on the work of the of the that has crafted a set of .
The WAI guidelines are grouped by priority; the priority 1 checkpoints are very similar to those in the final Section 508 rule. In fact, eleven of the sixteen 508 Standards are drawn directly from the Web Content Accessibility Guidelines, in some cases using language more consistent with regulatory language. Five of the 508 standards do not appear in the WAI checkpoints and require a higher level of access or give more specific requirements. On the other hand, there are four priority 1 WAI checkpoints that were not adopted by the Access Board. The differences between The WAI and Section 508 are discussed in the and in Jim Thatcher's .