Ace by DAISY vs IBM Equal Access Accessibility Checker
Ace by DAISY
daisy.orgIBM Equal Access Accessibility Checker
ibm.comSide by side
| Figure | Ace by DAISY | IBM Equal Access Accessibility Checker |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Web | — | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 2 |
| Spec score · Accessibility Testing Software | 8.3 (#52) | 9.0 (#7) |
| Audience | DAISY describes Ace as suitable for publishing teams, third party vendors, self publishing authors, and others testing EPUB files without digital rights management. | IBM describes the tools as intended for web developers and accessibility auditors. |
| Browser extension | No | The Chrome extension runs inside Developer Tools and helps locate accessibility problems and possible fixes. |
| CI/CD integration | Yes | Yes |
| Free plan | Yes | Yes |
| Purpose | Ace checks EPUB files for accessibility at any point in a publishing workflow and assists with evaluating conformance to the EPUB Accessibility Specification. | The checker automates accessibility checking of web content and applications for web developers and accessibility auditors. |
| Reports | Ace generates an HTML report covering violations, metadata, document outlines, and images. | XLSX output is included automatically, and JSON and other report formats can be configured. |
| Support | DAISY provides Ace support resources, including troubleshooting, FAQs, and contact links. | The project Wiki directs users to submit bugs, questions, and suggestions through GitHub issues. |
Plans
IBM Equal Access Accessibility Checker
- Free and open sourceFree
- Free/open-source toolkitFree
In their own words
Ace by DAISY
Ace by DAISY has no write-up on Specifiction yet; its figures are above.
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.