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.
AChecker a quality management solution for web sites developed by the Inclusive Design Research Center at OCAD. It checks your web site against the WCAG guidelines.
For the purpose of this ADE, we will use the web-based version of this tool to test a single live web page. (There is also a version you can download.)
The tool is very simple to use: copy a web address into the textbox and click the button marked "Check It". After a short wait, a resulting report is provided.
The report has five (5) tabs: Known Problems, Likely Problems, Potential Problems, HTML Validation, CSS Validation.
For the purpose of this ADE, we are only interested in the "Known Problems" tab. If you select the "Known Problems" tab, you will get a report of errors and warnings for all checkpoints assigned a specific WCAG priority level (provided in parenthesis) that may have been violated along with the text of the applicable WCAG guidelines.
Since some of the WCAG guidelines cannot be automated, 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.
Submit a report on what you
(and the AChecker tool) have
Note: You are not expected to be experienced web programmers. If you feel something is too difficult based on your current understanding, you may say it is difficult (where appropriate in your answers to questions 2) because the underlying HTML needs to be first researched/learned.
Be sure to include:
Micorosft also has an accessibility checker that is introduced
in a video.