How do I integrate axe-core with Jest?

Install the axe-core npm package and use a custom Jest setup to inject the axe script into your test environment, then call axe.run() in your test cases to check for violations. Community libraries like jest-axe can simplify this process.

Axe-core vs Lighthouse: which is better for accessibility?

Axe-core is a focused engine for integrating automated tests into development workflows, while Lighthouse is a broader auditing tool for performance and SEO. Axe-core offers deeper, configurable rules and zero false positives, but Lighthouse provides a quick, holistic scan in Chrome DevTools.

Does axe-core work with React or Vue?

Yes, axe-core can test React, Vue, or any HTML-based UI by running in a browser context during tests. For React, tools like @axe-core/react can help integrate it directly into development modes for real-time feedback.

Can axe-core test single-page applications?

Yes, it supports dynamic content and SPAs by allowing calls to axe.run() whenever new UI becomes visible, and it handles iframes and shadow DOM for component-based architectures.

How accurate is axe-core's automated testing?

Axe-core is highly accurate for the rules it covers, with a design goal of zero false positives, but it only automates about 57% of WCAG issues. Manual testing is still essential for full compliance, especially for context-dependent checks.

Is axe-core free for commercial use?

Yes, axe-core is open-source under the Mozilla Public License 2.0, allowing free use in commercial projects. However, Deque Systems offers paid extensions and support services.

Open-Awesome

axe-core

MPL-2.0JavaScriptv4.11.3

An accessibility testing engine for automated Web UI testing, integrating with existing test environments.

Visit Website GitHub

7.1k stars886 forks0 contributors

What is axe-core?

Axe-core is an open-source accessibility testing engine designed to automate the detection of WCAG violations in web interfaces. It integrates directly into existing test environments, allowing teams to run accessibility checks alongside functional tests. The engine is built to be fast, lightweight, and to provide reliable results without false positives.

Target Audience

Web developers, QA engineers, and development teams who need to incorporate automated accessibility testing into their CI/CD pipelines and daily workflows.

Value Proposition

Developers choose axe-core for its seamless integration with modern testing frameworks, zero false-positive guarantee, and comprehensive support for WCAG standards and ARIA roles, making it a trusted tool for building accessible web applications.

Overview

Accessibility engine for automated Web UI testing

Use Cases

Best For

Automating accessibility checks in unit and integration tests
Ensuring WCAG 2.x compliance during web development
Testing single-page applications (SPAs) and dynamic content
Integrating accessibility testing into CI/CD pipelines
Validating ARIA implementations and shadow DOM components
Localizing accessibility tests for international development teams

Not Ideal For

Projects needing 100% automated accessibility coverage without any manual review
Quick, one-off scans without integrating into a testing framework or build process
Environments relying solely on JSDOM for all testing, especially color-contrast checks

Pros & Cons

Pros

Comprehensive WCAG Coverage

Tests for WCAG 2.0, 2.1, and 2.2 at levels A, AA, and AAA, plus best practices, as documented in the rule descriptions.

Zero False Positives

Engineered to return accurate results without false positives, reducing noise in test reports, as stated in the manifesto.

Seamless Integration

Works with modern browsers, testing environments, and frameworks like unit and integration tests, fitting into existing workflows.

Localization Support

Supports multiple languages via locale files, allowing international teams to run tests in their native language.

Cons

Incomplete Automated Detection

Only catches about 57% of WCAG issues automatically, per the README, requiring manual review for 'incomplete' results and complex cases.

Limited JSDOM Compatibility

Key rules like color-contrast do not work with JSDOM, hindering testing in Node.js environments without a real browser.

Sparse Browser Testing

Only Chrome and Firefox are tested on every pull request, potentially leading to untested bugs in Safari, Edge, or deprecated IE.

Frequently Asked Questions

Related Projects

Puppeteer

JavaScript API for Chrome and Firefox

Stars94,169

Forks9,409

Last commit2 days ago

Playwright

Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.

Delightful JavaScript Testing.

Stars45,333

Forks6,646

Last commit4 days ago

Mocha

☕️ Classic, reliable, trusted test framework for Node.js and the browser

Stars22,882

Forks3,066

Last commit2 days ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub

axe-core

MPL-2.0JavaScriptv4.11.3

An accessibility testing engine for automated Web UI testing, integrating with existing test environments.

Visit Website GitHub

7.1k stars886 forks0 contributors

What is axe-core?

Target Audience

Web developers, QA engineers, and development teams who need to incorporate automated accessibility testing into their CI/CD pipelines and daily workflows.

Value Proposition

Overview

Accessibility engine for automated Web UI testing

Use Cases

Best For

Automating accessibility checks in unit and integration tests
Ensuring WCAG 2.x compliance during web development
Testing single-page applications (SPAs) and dynamic content
Integrating accessibility testing into CI/CD pipelines
Validating ARIA implementations and shadow DOM components
Localizing accessibility tests for international development teams

Not Ideal For

Projects needing 100% automated accessibility coverage without any manual review
Quick, one-off scans without integrating into a testing framework or build process
Environments relying solely on JSDOM for all testing, especially color-contrast checks

Pros & Cons

Pros

Comprehensive WCAG Coverage

Tests for WCAG 2.0, 2.1, and 2.2 at levels A, AA, and AAA, plus best practices, as documented in the rule descriptions.

Zero False Positives

Engineered to return accurate results without false positives, reducing noise in test reports, as stated in the manifesto.

Seamless Integration

Works with modern browsers, testing environments, and frameworks like unit and integration tests, fitting into existing workflows.

Localization Support

Supports multiple languages via locale files, allowing international teams to run tests in their native language.

Cons

Incomplete Automated Detection

Only catches about 57% of WCAG issues automatically, per the README, requiring manual review for 'incomplete' results and complex cases.

Limited JSDOM Compatibility

Key rules like color-contrast do not work with JSDOM, hindering testing in Node.js environments without a real browser.

Sparse Browser Testing

Only Chrome and Firefox are tested on every pull request, potentially leading to untested bugs in Safari, Edge, or deprecated IE.

Frequently Asked Questions

Related Projects

Puppeteer

JavaScript API for Chrome and Firefox

Stars94,169

Forks9,409

Last commit2 days ago

Playwright

Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.

Delightful JavaScript Testing.

Stars45,333

Forks6,646

Last commit4 days ago

Mocha

☕️ Classic, reliable, trusted test framework for Node.js and the browser

Stars22,882

Forks3,066

Last commit2 days ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub