AccessLint vs axe-core

AccessLint checks accessibility during development, on pull requests, and on live sites. Its WCAG 2.2 engine has 95 rules and a stated 53ms median audit across 5,000 real-world sites. Pull-request reviews inspect changed files and leave inline comments with the relevant rule and a suggested correction, but do not fail builds or block merges. Deploy-triggered scans require Starter or Pro, run asynchronously, and also do not synchronously fail builds. Saved user journeys can run daily, with email alerts for new violations or changes against a baseline. The toolkit provides checks for Playwright, Vitest, and Storybook, while pull-request reviews use a GitHub App. Starter and Pro include shareable read-only evidence reports with before-and-after screenshots of affected elements. Free covers public-repository pull-request reviews, one daily monitored flow, and violation trends. Starter costs $19 a month or $190 a year; Pro costs $349 a month or $3,490 a year. AccessLint says automated checks alone cannot make a site compliant.

axe-core is a free, open-source accessibility testing engine for websites and other HTML-based interfaces. It is designed to run beside functional tests in unit, integration, browser, and other testing environments. Its rules cover WCAG 2.0, 2.1, and 2.2 at A, AA, and AAA levels, along with additional best practices. Deque says automated checks find an average of 57% of WCAG issues, while uncertain findings are marked for manual review. Installation is documented through npm or pnpm, with tests calling the axe.run() API. The API lists Microsoft Edge, Google Chrome, Mozilla Firefox, and Apple Safari; Internet Explorer 11 is deprecated. Chrome and Firefox are tested on every pull request. JSDOM support is limited, and color-contrast checks do not work there. axe-core uses the Mozilla Public License 2.0. Security updates are available for minor lines up to 18 months old. Vulnerabilities are requested by email, with a stated 24-business-hour response and no bug bounty.