WebAIM - Web Accessibility In Mind

Accessibility Evaluation Tools

WebAIM Accessibility Testing Services

The experts at WebAIM can audit your web site and provide a detailed report to help you remediate accessibility and WCAG compliance issues.


Many web designers, developers, and evaluators are introduced to web access through accessibility tools. All accessibility tools perform automated checks of web pages for accessibility issues and all generally have additional features, but each tool targets different audiences. In order to help web designers, developers, and evaluators choose an appropriate tool for their purposes, this article discusses the general types or classifications of accessibility tools.

However, web accessibility requires more than just accessibility tools; it requires human judgment. It is important to remember that accessibility tools can only partially check accessibility through automation. The real key is to learn and understand the web accessibility standards rather than relying on a tool to determine if a page is accessible or not.


No automated evaluation tool can tell you if your site is accessible, or even compliant. Human testing is always necessary because accessibility is about the human experience.

Classifications of Accessibility Evaluation Tools

A feather duster and a sledge hammer There are many different types of evaluation tools that can be used to determine whether or not web content is accessible. This section will focus on the classification and usage of different evaluation tools, and what web designers, developers and evaluators should know about these classifications.

Standards and guidelines used

One key in understanding accessibility tools is to understand the standards to which the tool was developed. When deciding which accessibility tool will work best for you it is important to consider the standards and guidelines used by the different accessibility evaluation tools. The current standard is the Web Content Accessibility Guidelines version 2.1 (“WCAG 2”).


WCAG 2 (currently in version 2.1) consists of three priority levels that act as an industry standard. The first level, Level A, covers items on web pages that must be made accessible in order for individuals with disabilities to access the content at all. The second level, Level AA, includes items on web pages that should be made accessible to allow a wider group of users to access the content. Level AAA describes items on web pages that can be made accessible to allow the widest amount of individuals with disabilities to use the site..

Section 508

Prior to January 2018, Section 508 of the United States Rehabilitation Act outlined a separate set of requirements for making federally-funded web sites accessible. Section 508 still requires accessibility, but now uses WCAG 2.0 (the predecessor to WCAG 2.1) Level A and AA as its benchmark.

Testing tools that report only on Section 508 standards are outdated.

Free vs. commercial

One very important classification of tools to the budget conscious web designer, developer, or evaluator is the cost. There are many excellent free evaluation tools out there, but perhaps after weighing the specific needs of your organization and the features you need you may decide that a commercially available tool is best for you. When this decision is made it will be important to keep in mind:

  • Who will be using the tool. The evaluation tool, and its associated cost, will depend a great deal on the accessibility knowledge of the one using it. Free tools often assume a greater understanding and spend less time educating their user.
  • The size of the site being examined. Those tasked with maintaining or creating a very large web site will need accessibility tools that spider through the site so they don't have to check the site one page at a time. Often times it is the commercially available tools that have this feature. Free tools often limit their scope to checking just one page at a time.
  • The information that must be collected. This varies depending on your situation. Some developers may be required to provide detailed reports on the accessibility of many different types of web documents. Commercially available tools often produce more detailed and specific reports.


Another important classification of accessibility evaluation tools involves where these tools are meant to function. Some tools are available at a web site where they are able to evaluate the content of a page quickly and easily without downloading or installing an application. Other options include tools that are created as extensions to a browser, tools that function as part of a web authoring tool. Finally, some tools require installation on your hard drive or server like other pieces of software.

Online service

There are many tools, and especially free ones, that are used online. They work by having the site visitor input the URL of their web page, selecting from any evaluation options, and then selecting a "Go" button or some other method of initializing the program.

Within a browser

Several accessibility tools have been created as extensions for the more popular Internet browsers. After being downloaded and installed they provide extra menu options within the browser itself. Some of these extensions create toolbars that remain visible within the browser. All accessibility extensions provide a variety of useful tasks to evaluate the page that is currently in the browser window.

Within an authoring tool

Some accessibility evaluation tools have been created to function as part of a web authoring tool, like Dreamweaver, in Word Proccessing Tools like Microsoft Word, or in content management systems. These plugins and extensions allow web developers to examine their content for accessibility in the same environment they are using to create this content. This would increase the likelihood that accessibility evaluation steps will take place.

Install on hard drive

Many of the more powerful accessibility evaluation tools require that they be installed on your hard drive or server like other pieces of software. These tools are useful when working on very large and complex sites. They are able to examine web pages local to your machine or behind your company's firewall.


Accessibility evaluation tools can also be classified in terms of what they examine or their scope. Some tools are simple and limited in scope so they evaluate just one page at a time and check for just a few things. Other tools are very specific in what they evaluate and focus on just one element of a web site. Then there are very detail oriented tools that are able to examine large sites and check for a variety of errors.

One page at a time

Tools that evaluate just one page at a time are often those accessibility evaluation tools found online and as part of a browser. Their functionality is limited to evaluating content found at just one URL, but they often can provide very rich details about the page's accessibility.

Specific items

Many accessibility tools focus on just one element of a web site. They may demonstrate what the site looks like to someone who is blind or has low vision. Some tools may show the site content from the perspective of someone who is colorblind. This limited scope is is commonly found in tools available online and as part of a browser.

Site wide

Accessibility evaluation tools that require installation of software are often able to examine large sites and check for a variety of errors. These tools are meant for enterprise level organizations with a large web development staff, and more specific requirements. This is a feature found in commercial software tools.

Evaluation only vs. evaluation and repair

Another important classification of accessibility evaluation tools deals with the repair functionality of these tools. Many tools can only perform an evaluation, but some tools are able to perform the evaluation and/or guide the repair process. This is a more common characteristic of commercially available tools. These often spend time educating their user and guiding both the evaluation and repair process.

Report styles

Accessibility tools generate a variety of reports based on the results of an analyzed web page. All quality accessibility tools should look at a web page for both obvious errors (such as missing alternative text for images) and warn users of the need for manual checks (i.e. the appropriateness of the alternative text for the image). However, beyond the general requirement for tools, accessibility report styles differ widely depending on the target audience familiarity with web design and web accessibility standards. Web designers, developers, and evaluators who know which style best meets their needs will be able to choose an appropriate tool.


Text-based report styles are the most common type of accessibility report. These reports generally list the specific guideline being used to scan the page and the instances of each type of accessibility error. Some also show the source code of the page where the error occurs.


This report style uses special icons to highlight accessibility errors and manual check issues on a web page. With this kind of report, the icons are integrated into the web page's graphical user interface next to the item on the page with an accessibility issue.

EARL report

An Evaluation and Reporting Language (EARL) report is a machine readable report of the accessibility standard the page validates to, as well as the accessibility issues highlighted in the report, the date of the evaluation, and any manual checks that need to be performed by developers. The EARL reports are an attempt by the W3C to standardize accessibility reports and help users compare the effectiveness of accessibility tools.

Which Tool is Best?

Depending on your needs, different types or classifications of evaluation tools offer different report formats, additional features, and benefits that can help you choose a tool for your situation. So which tool is right for you? That depends on your skill set and how you define your web responsibilities.

It's often best to use a variety of tools to test various aspects of web accessibility and to get varying feedback and reports to ensure you are capturing all possible issues. But remember, automated testing alone is not sufficient - you will still need manual testing to ensure your content is actually accessible.