This ADE will provide you with a quick introduction to evaluating computer accessibility. As with the Before and After Considering Accessibility ADE, this ADE continues using the Web for practical examples of technology access.
In this ADE your goal will
be to determine to what level a specific website adheres to the
recommendations of the Web Content Accessibility Guidelines (WCAG)
developed by the World Wide Web Consortium (W3C) as part of their Web
Accessibility Initiative (WAI). Most of the work will be done
by an online accessibility evaluation tool.
At the end of this ADE, you will have gained familiarity with an automated accessibility validation tool and how to apply generic recommendations to evaluating an interface.
Note: Several abbreviations and acronyms are used on this page. To help you, they have been marked with <abbr> or <acronym> tags as needed. Theoretically, two groups of users can benefit from these HTML elements:
WCAG is part of a series of accessibility guidelines, including the Authoring Tool Accessibility Guidelines (ATAG) and the User Agent Accessibility Guidelines (UAAG). WCAG is primarily intended for:
WCAG 2.0 is the current version of WCAG. It is organized around four design principles each having several guidelines which then have success criteria at level 1, 2, or 3. Success criteria are the testable statements that define how Web content conforms to WCAG 2.0 . Each success criteria has a list of sufficient techniques and common failures. If you implement the sufficient techniques, you meet the success criteria for a particular level. If you have one of the common failures, you do not meet the guidelines for a particular level.
WCAG 2.0 also defines three levels of conformance:
More information is available
at the Web Accessibility Initiative homepage. WCAG will be
discussed in more detail later in the course.
To help you to complete this ADE, you may wish to review information from the Before and After Considering Accessibility ADE.
Wave is a popular and powerful free web accessibility evaluation tool.
The tool is very simple to use: copy a web address into the text box and click the button marked "Check It". After a short wait, a resulting report is provided.
The report has five (5) tabs: Summary, Detals, Reference, Structure, and Contrast. When you first entre a web address, the Summary page comes up once the evaluation is complete. While this gives a quick indication of the quantity and range of errors an alerts, the Details page is most important for actually seeing what types of accessibility probems a site contains. If you click on the (i) in the error or alert message in the Details tab it will provide a description of the problem and a link to the WCAG guideline success criteria that is being violated. We will not be concerned about the last two tabs in this ADE.
You will likely find more alerts than errors. This is because some of the WCAG guidelines cannot be evaluated in a fully automated manner. They will require further (manual) investigation to determine whether their related issues applies to the website as well as whether the website complies with the guideline.
We will focus on the Errors, Contrast Errors and Alerts on the Summary and Details tab.
You will also find information on the sturctue of the website an on ARIA issues that have been identified. ARIA stands for Accessible Rich Internet Applications, which "defines a way to make Web content and Web applications more accessible to people with disabilities. It especially helps with dynamic content and advanced user interface controls developed with HTML, JavaScript, and related technologies." We will not be dealing with ARIA or ARIA issues in this ADE.