Skip to content
SPECIFICTION
Get listed

IBM Equal Access Accessibility Checker vs Open Scans

IBM Equal Access Accessibility Checker

ibm.com

Open Scans

mgifford.github.io

Side by side

FigureIBM Equal Access Accessibility CheckerOpen Scans
Price fromFreeFree
Free planYesYes
Free trial——
Open sourceYes—
WebYesYes
APIYes—
Self-hostedYesYes
Plans published21
Spec score · Website Accessibility Tools9.0 (#6)8.2 (#38)
CI/CD integrationYesYes
PrivacyThe project wiki says web data remains local, with rules and engine downloaded and run locally rather than sent to servers.Scan results are published publicly to GitHub Pages, and the documentation says not to submit URLs that should remain private.
PurposeThe checker automates accessibility checking of web content and applications for web developers and accessibility auditors.Open Scans checks websites for accessibility issues using multiple WCAG 2.2 scanning engines.
ReportsXLSX output is included automatically, and JSON and other report formats can be configured.Interactive HTML reports are published to GitHub Pages, and the reports page lists links to HTML, Markdown, CSV, and JSON reports.
Scan scopepagesite
SupportThe project Wiki directs users to submit bugs, questions, and suggestions through GitHub issues.The project directs users who need help to workflow run logs and troubleshooting guidance in its repository documentation.
WCAG versionwcag 2.2wcag 2.2
What it doesIBM Equal Access Accessibility Checker automates accessibility checks in browsers and continuous-development environments.Open Scans is a free, open-source tool for scanning websites for accessibility issues with multiple WCAG 2.2 engines.

Plans

IBM Equal Access Accessibility Checker

  • Free and open sourceFree
  • Free/open-source toolkitFree

IBM Equal Access Accessibility Checker pricing →

Open Scans

  • Open ScansFree

Open Scans pricing →

In their own words

IBM Equal Access Accessibility Checker

IBM Equal Access Accessibility Checker automates accessibility checks for web content and applications, with tools aimed at web developers and accessibility auditors. Its rule engine connects checks to accessibility standards, including WCAG 2.2, and scans at page level. Results can identify the issue type, applicable WCAG success criteria, affected element, XPath, progression level, and a help link. Browser extensions are available for Chrome, Firefox, and Edge. They work in browser DevTools and include a visualization mode for keyboard checking. For CI/CD workflows, packages are available for Node, Cypress, and Java; the project Wiki also lists a Karma plugin and names Selenium, Puppeteer, Playwright, and Zombie as testing or parsing engines. The extension can combine up to 50 stored scans into a Microsoft Excel report. The Wiki says web data, rules, and the engine stay local rather than sending web data to servers or third parties. The tool is free at free. IBM cautions that automated checks cover only part of its accessibility requirements, so manual and screen reader testing should follow.

Visit ibm.com

Open Scans

Open Scans has no write-up on Specifiction yet; its figures are above.

Visit mgifford.github.io