Sparkbox's Automated Accessibility Tool Reviews

Introduction: Automated Accessibility Testing Tools Reviews

There are a lot of automated accessibility tools out there. So how do you decide which one to use? We've started a new research initiative, reviewing different options to help you decide which tool is right for your project.

axe Browser Extension

While the free axe browser extension caught most of the issues we expected and more from our issue list, it doesn’t replace manual testing to catch accessibility issues with things like keyboard navigation and non-specific link text. Learn the strengths and weaknesses of the axe Browser Extension.

Google Lighthouse

Lighthouse is a very diverse tool that can be set up and used in a variety of ways, which makes it a good option for both technical and non-technical users and it can be included as part of a continuous integration pipeline. Learn the strengths and weaknesses of Google Lighthouse.

WAVE Browser Extension

Utilizing the WAVE browser extension is a quick and easy way to begin improving or developing an accessibility workflow with its easy-to-use UI that allows users to analyze their site for issues and also improve their overall knowledge of accessibility. Learn the strengths and weaknesses of the WAVE Browser Extension.

Pa11y

Although Pa11y has some challenges with its prerequisites and configuration for more robust testing, its flexibility makes it a very strong tool in your accessibility toolbox. Learn the strengths and weaknesses of Pa11y.

ANDI

ANDI has some convenient features. But with a lack of reputable sources, it’s hard to recommend ANDI as a primary tool. However, it could act as a secondary tool to quickly verify any immediate issues to then research. Learn the strengths and weaknesses of ANDI.

axe Accessibility Linter

A linter enables early and frequent feedback at the beginning of a developer’s workflow. The axe linter is no exception. This review focuses solely on the linter’s performance but should be considered a tool within a larger, more comprehensive, accessibility analysis toolchain. Learn the strengths and weaknesses of the axe Accessibility Linter for VS code.

PayPal’s AATT

PayPal’s Automated Accessibility Testing Tool requires the user to download the code and use the command line, causing a barrier to ease of use and installation for anyone unfamiliar with the command line or Git. Learn the strengths and weaknesses of PayPal's AATT.

Stark for Figma

Web accessibility should be a consideration throughout the entire process—including the UX and design stages. Let's take a look at the Stark plugin for Figma by using it with a test page put together by our design team. Learn the strengths and weaknesses of the Stark Accessibility Testing Tool.

IBM Equal Access

IBM’s browser extension has some nice features that set it apart from similar tools, and its baseline issue detection is robust, even though it can’t catch everything. Learn the strengths and weaknesses of IBM’s Equal Access Accessibility Checker browser extension.