Photo Credit: Jeff Miller, UW-Madison University Communications |
“The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.” (Tim Berners-Lee) |
Key Information About Web Accessibility
What are some common accessibility problems?
- Images without Alt text (for those who cannot see the image)
- Using tables for layout in a way that changes the meaning or understandability of the content when read linearly (e.g., when using a linearizer tool such as the developer toolbar extension for Firefox)
- Not including captions or audio descriptions in multimedia
- Including only a visible form of a CAPTCHA that you must get through to use a site
- Content that times out without way to get more time
- Information coded in color only
- Lack of Keyboard access to all functionality
- Low contrast
- Using more complex language than is necessary.
- Content that functions in an unpredictable, inconsistent or confusing manner
- Using plug-in content (applets etc) that aren't accessible (with no alternative)
- Creating forms that are not accessible
Where can I find out how to make Web sites accessible?
- The W3C’s Web Accessibility Initiative is a good starting point. From there, you can find other resources. The articles called Getting Started: Making A Web Site Accessible and How People with Disabilities Use the Web are especially useful.
- If you work for the government, check out Web-based Intranet and Internet Information and Applications (1194.22).
- The Trace Center's Selected Resources about Web Accessibility.
Even if I don’t know much about HTML, can I use a Web authoring tool to create an accessible site?
Yes, you can. Some tools even have accessibility test tools built right into them. When purchasing an authoring tool, be sure to check for its support of accessibility features. There is even a set of accessibility guidelines for authoring tools, called “Authoring Tool Accessibility Guidelines” (ATAG), so you could check ATAG for conformance of your authoring tool.
Do I have to create a “text-only” version of my site to meet accessibility guidelines?
No. In fact, it is not recommended. Text-only sites are not as accessible as HTML pages and generally should not be used.
Do Bobby and other automatic Web evaluation tools reliably tell me if my page is accessible?
Automated tools can be helpful in locating some types of errors, and they are fast and convenient. However, many types of access barriers cannot be detected by an automated tool. The tools will also give you many warnings that may or may not be problems. Automated tools are very useful, but they will not give you a definitive answer regarding the accessibility of your page or site.
How does WCAG 2.0 differ from WCAG 1.0?
Web Content Accessibility Guidelines 1.0 was “HTML-centric” and did not allow use of many other technologies, even though they have become accessible. WCAG 2.0 is written to be more technology-independent. It provides the general guidelines and specific success criteria, but does not prescribe specific solutions. An accompanying document, however, provides very detailed examples of techniques that are sufficient to meet each success criterion. WCAG 2.0 is also more testable than 1.0, making it easier to determine if you have conformed.
For an overview of WCAG 2.0 requirements and techniques, refer to How to Meet WCAG 2.0. For a comparison of WCAG 1.0 and 2.0, refer to Comparison of WCAG 1.0 checkpoints to WCAG 2.0.
Web Accessibility Work at Trace
The Trace Center has been a leader in efforts to create a more accessible internet since 1994, when it developed the first Web Accessibility Guidelines. Trace’s Unified Web Accessibility Guidelines (Version 8) later became the starting point for the work of the W3C’s Web Accessibility Initiative. Trace provided the co-chair and two editors for the Web Content Accessibilit y Guidelines 1.0 and 2.0 (now in the Last Call process). In addition Trace has worked with others on development of contrast measures and tools, and on seizure disorder measures (including release of a free photosensitive seizure content analysis tool). This work, and especially Trace’s partnership with the Web Accessibility Initiative, has been supported by the National Institute on Disability and Rehabilitation Research (grant #H133E030012 and #H133E980008).
|
|
|
