Horn vs IBM Equal Access Accessibility Checker
Horn
horn.report
IBM Equal Access Accessibility Checker
ibm.comSide by side
| Figure | Horn | IBM Equal Access Accessibility Checker |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Web | Yes | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 2 |
| Spec score · Accessibility Testing Software | 8.3 (#53) | 9.0 (#7) |
| Purpose | Horn is an open-source PDF/UA checker based on the Matterhorn Protocol. | The checker automates accessibility checking of web content and applications for web developers and accessibility auditors. |
| Reports | Horn supports SARIF, JUnit XML, JSON, and human-readable text output. | XLSX output is included automatically, and JSON and other report formats can be configured. |
Plans
IBM Equal Access Accessibility Checker
- Free and open sourceFree
- Free/open-source toolkitFree
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.