IBM Equal Access Accessibility Checker

IBM Equal Access Accessibility Checker brings accessibility scans into browsers and automated test workflows. It is best suited to web developers and accessibility auditors who want standards-linked findings alongside their existing work. Its main limitation is that automated checks cover only part of accessibility requirements.

Overview

The checker maps its rules to accessibility standards, including WCAG 2.2, and scans individual pages. Results can identify the issue type, affected element and XPath, relevant success criteria, progression level, and a help link. That context can help a developer locate and interpret a finding rather than merely see a pass-or-fail outcome.

The project Wiki says the rules and engine run locally, web data stays on the user's device, and web data is not sent to servers or transferred to third parties. That makes the tool a practical option for teams that want local scanning. Its scope remains a first check, not a complete accessibility assessment: IBM says automated checks cover only a subset of its accessibility requirements and should be followed by manual and screen reader testing.

Key features

• Browser extensions: Chrome, Firefox, and Edge extensions integrate with browser DevTools. A keyboard checker mode visualization adds a way to examine keyboard behavior alongside scan results, which is useful for developers and auditors working directly on a page.
• Automated testing: 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 teams several routes to include checks in development and test workflows, although it does not replace manual review.
• Scan reports: The extension can combine up to 50 stored scans into a Microsoft Excel report. That is useful for consolidating a modest batch of browser scans; the stated cap makes it less suited to compiling larger scan sets in one report.
• API access: API support adds another integration option for developers, alongside the browser extension and CI/CD packages.
• Project support: The project Wiki directs users to GitHub issues for bugs, questions, and suggestions. Users should be comfortable turning to that channel for project support.

Pricing

The Free and open source plan costs nothing and includes browser extensions and CI/CD and automated testing packages. There is no paid tier or free trial stated for this product; the free plan is the offering. It fits individual developers, auditors, and teams that want to add automated scans without a software charge. There is no published seat or scan quota beyond the extension's limit of 50 stored scans per Excel report.

Platforms

The checker is available as an API, browser extension, and web tool. Extensions are named for Chrome, Firefox, and Edge, while CI/CD options include packages for Node, Cypress, and Java plus a Karma plugin named in the project Wiki. The range favors web teams choosing between browser-based review and automated testing rather than users seeking a standalone desktop application.

Who it's for

IBM describes the tools as intended for web developers and accessibility auditors. Developers can use page-level findings to locate issues and bring scans into automated workflows; auditors can use the browser tools and stored-scan reports as part of an assessment. Neither audience should rely on the automated results alone: manual and screen reader testing remain necessary.

Pros and cons

• Pro — Findings include locating detail: Element and XPath information, success criteria, issue type, and a help link can make it easier to act on scan results.
• Pro — Multiple workflow options: Browser extensions, API access, and CI/CD packages support both page review and automated testing.
• Pro — Local processing: The project Wiki says web data stays local and is not sent to servers or third parties.
• Con — Automation has limited coverage: IBM says the checks cover only a subset of its accessibility requirements, so a scan cannot stand in for manual and screen reader testing.
• Con — Page-level scan scope: The stated scope is a page, so this is not a single scan of an entire site.
• Con — Report aggregation is capped: An Excel report can combine up to 50 stored scans, which may constrain larger reporting batches.

Alternatives

Compare other options in Accessibility Testing Software or Website Accessibility Tools. Choose WAVE if its freemium model and API, extension, Linux, macOS, web, and Windows platforms better match your setup; its subscription API starts at a 250-credit minimum purchase for $10 a month.

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

axe-core is a free, open-source accessibility testing engine under the MPL-2.0 license, with API, extension, and web platforms. Accessibility Insights for Web is a free, open-source alternative for Chrome and Microsoft browser users.

Gamyata may be a better fit for a small monthly page allowance: its free plan covers 5 pages per month and includes a document allowance and email support. Total Validator has a free download with a one-page summary for a single web page, plus a paid Basic plan at $10, paid once; consider it if those terms suit your needs.

pour is another free option, with all tools and no accounts, subscriptions, or paid tiers.

Verdict

IBM Equal Access Accessibility Checker is a strong fit for developers and accessibility auditors who want a free way to run standards-mapped page checks in a browser or CI/CD workflow, with findings detailed enough to guide follow-up. Choose it for that workflow flexibility and local processing; look elsewhere if you need automated results to stand in for a complete accessibility evaluation, or need scans beyond individual pages.