IBM Equal Access Accessibility Checker

IBM Equal Access Accessibility Checker is a free tool for finding web accessibility issues in browser scans and automated test workflows. It suits web developers and accessibility auditors who want standards-linked findings close to their work. Its scans are a useful first pass, but full accessibility review still calls for manual and screen reader testing.

Overview

The checker scans individual pages and maps its rules to accessibility standards, including WCAG 2.2. Findings can identify the issue type, affected element and XPath, relevant success criterion, progression level, and a help link. That context helps developers locate issues and understand which requirement they relate to.

The project Wiki says the rules and engine run locally, and web data stays on the device rather than being sent to servers or third parties. This makes the checker a sensible option for teams that want to scan pages without transmitting their web data. The trade-off is coverage: automated checks address only a subset of accessibility requirements, so the checker cannot stand in for manual and screen reader testing.

Key features

• Browser extensions: Extensions for Chrome, Firefox, and Edge integrate with browser DevTools. A keyboard checker mode visualization gives developers and auditors another way to inspect keyboard behavior while working on a page.
• Automated test integration: Packages are available for Node, Cypress, and Java, and the project Wiki also names a Karma plugin. It identifies Selenium, Puppeteer, Playwright, and Zombie as testing or parsing engines for CI/CD packages. This gives development teams several routes to add checks to existing automated workflows.
• Scan reports: The browser extension can combine up to 50 stored scans into a Microsoft Excel report. That can help auditors collect findings across multiple pages, though it does not expand the page-level scan scope.
• Issue context: Results can include issue type, WCAG success criteria, element, XPath, progression level, and a help link. These details make findings more useful for tracking down and addressing specific issues.
• API access: API access provides another way to use the checker alongside browser extensions and CI/CD packages.

Pricing

The Free and open source plan costs nothing and includes browser extensions plus CI/CD and automated testing packages. With no paid tier or free-plan cap described, it is a practical starting point for individual developers and teams that want standards-based checks without a software fee. The main limit is the checker’s partial automated coverage, which makes additional manual and screen reader review necessary.

Platforms

The checker supports API, extension, and web use. Its browser extensions are available for Chrome, Firefox, and Edge, while CI/CD packages cover Node, Cypress, and Java. Local execution of the rules and engine is a useful privacy feature for web teams; users seeking a full-site automated scan should note that the scan scope is a page.

Who it's for

IBM describes the tools as intended for web developers and accessibility auditors. Developers can use browser findings to locate page issues and connect checks to automated test workflows. Auditors can collect scan results and export up to 50 stored scans to Excel. In either role, the tool works best as one layer of review, with manual and screen reader testing used to assess requirements that automation does not cover.

Pros and cons

• Pros: Free access includes both browser extensions and CI/CD packages, so teams can add checks to page work and automated workflows without choosing a paid plan.
• Pros: Standards references and element-level details, including XPath and help links, give developers useful context for investigating findings.
• Pros: The project Wiki says web data remains local and is not sent to servers or third parties.
• Cons: Scans cover individual pages, and automated checks address only a subset of accessibility requirements; they need to be followed by manual and screen reader testing.
• Cons: Support for bugs, questions, and suggestions runs through GitHub issues, which may not suit users looking for another support channel.

Alternatives

WAVE is worth considering if you want a freemium option with API, extension, desktop, and web platforms; its Subscription API costs $10 a month, with a 250 credit minimum purchase.

Alfa is another free option, distributed as separate npm packages under the MIT license, with API, desktop, self-hosted, and web platforms.

Axe DevTools offers a free extension that checks one page at a time and a Pro extension with AI-enhanced features and intelligent guided testing.

Evinced may suit readers seeking a paid product with a trial: its Site Scanner trial runs for 14 days without a credit card and allows up to 50,000 URLs crawled.

axe-core is a free, open-source accessibility testing engine under the MPL-2.0 license, with API, extension, and web platforms.

Gamyata offers a free plan for five pages per month, a document allowance, and email support; its Starter plan includes 100 pages per month and five users.

Scanpoof starts at $29 a month for one website and up to 10 pages scanned daily, with WCAG 2.1 / 2.2 AA testing and email regression alerts.

Welcoming Web offers a free plan with a core accessibility widget and basic features, as well as a Pro plan from $19 a month.

For more options, browse Accessibility Testing Software or Website Accessibility Tools.

Verdict

Choose IBM Equal Access Accessibility Checker if you are a web developer or accessibility auditor looking for a free way to add page scans to browser work and CI/CD workflows, with findings that point to relevant standards and page elements. Look elsewhere if you need more than page-level automated checks; whatever tool you choose, IBM’s checker still requires manual and screen reader testing to cover accessibility requirements automation misses.