[Atomic Glue](atomicglue.co)
ACCESSIBILITY
Home › Glossary › Accessibility· 48 ·

axe-core

/æks kɔːr/noun (proper)
Filed underAccessibilitySoftware EngineeringDevops
In brief · quick answer

axe-core is an open-source accessibility testing engine developed by Deque Systems. It is the industry-standard library for automated accessibility testing, integrated into browsers, CI/CD pipelines, and testing frameworks. axe-core runs a set of rules against a page's DOM and reports violations with WCAG success criterion mappings, element selectors, and fix guidance.

§ 1 Definition

axe-core is a JavaScript library that programmatically audits web pages for accessibility violations. Developed and maintained by Deque Systems, it powers axe DevTools browser extensions, axe for automated testing in CI/CD (Playwright, Cypress, Selenium), and several third-party tools. axe-core is widely regarded as the market leader in automated accessibility testing because it is designed to produce zero false positives by default. When axe-core reports a violation, it is almost always a genuine issue. The engine runs a set of rules corresponding to WCAG success criteria, checks the DOM against each rule, and returns a structured result array with severity (critical, serious, moderate, minor), WCAG conformance references, the specific HTML element involved, and a suggested fix. axe-core catches issues such as missing alt text, low colour contrast, missing form labels, incorrect ARIA attributes, duplicate IDs, and heading hierarchy problems. It is designed to run client-side in the browser or server-side in Node.js test suites.

§ 2 Why axe-core? Zero false positives

axe-core's design philosophy is that a testing tool must be trustworthy. False positives waste developer time and erode confidence in the tool. axe-core sacrifices breadth of detection (it will not catch every possible issue) for precision (every issue it reports is real and actionable). This makes it ideal for CI/CD integration, where a false-positive-driven build failure is destructive. Deque reports that axe-core detects approximately 57 percent of all accessibility defects, which combined with manual testing (keyboard, screen reader) yields a comprehensive coverage picture. The engine is also modular: you can include or exclude specific rules.

§ 3 Integrating axe-core into your workflow

Browser extension: axe DevTools browser extension for Chrome, Firefox, and Edge provides a one-click analysis within DevTools and is the fastest way to spot-check a page. CI/CD: axe-core integrates with Playwright (@axe-core/playwright), Cypress (cypress-axe), Selenium, and Puppeteer. Run it as part of your end-to-end test suite to catch regressions per commit. CLI: axe-core can also run via the axe-cli npm package for quick command-line scans. Best practice: run axe-core in CI on every PR, use the browser extension during development, and follow up with manual keyboard and screen reader testing before release.

§ 4 In code

// axe-core with Playwright
import { test, expect } from '@playwright/test';
import AxeBuilder from '@axe-core/playwright';

test('homepage should have no critical violations', async ({ page }) => {
  await page.goto('https://atomicglue.com');
  const results = await new AxeBuilder({ page }).analyze();
  const critical = results.violations.filter(v => v.impact === 'critical');
  expect(critical.length).toBe(0);
});

§ 5 Common questions

Q. Is axe-core the same as axe DevTools?
A. axe-core is the open-source engine. axe DevTools includes axe-core plus a browser extension, a dashboard, and premium features like guided testing and result management. The core engine is free and open source. The DevTools product is Deque's commercial offering.
Q. Does axe-core catch every accessibility issue?
A. No automated tool can. axe-core aims for zero false positives, which means it prioritises accuracy over coverage. It will not catch issues that require human judgment, such as whether alt text is appropriate, whether the focus order is semantically correct, or whether ARIA is used appropriately. Always pair axe-core with manual testing.
Key takeaways
  • axe-core is the industry standard for automated accessibility testing.
  • Designed for zero false positives. Every violation is actionable.
  • Integrates with Playwright, Cypress, Selenium, and CI/CD pipelines.
  • Catches approximately 57% of defects. Manual testing fills the rest.
  • Free and open source. Powers axe DevTools and many third-party tools.
How Atomic Glue helps

Atomic Glue runs axe-core in CI on every project, catching regressions before they ship. We combine automated scans with manual testing for comprehensive coverage. Our Web Development services include axe-core-based accessibility gates. Get in touch.

Get in touch
# axe-core

axe-core is an open-source accessibility testing engine developed by Deque Systems. It is the industry-standard library for automated accessibility testing, integrated into browsers, CI/CD pipelines, and testing frameworks. axe-core runs a set of rules against a page's DOM and reports violations with WCAG success criterion mappings, element selectors, and fix guidance.

Category: Accessibility (also: Software Engineering, Devops)

Author: Atomic Glue Team

## Definition

axe-core is a JavaScript library that programmatically audits web pages for accessibility violations. Developed and maintained by Deque Systems, it powers axe DevTools browser extensions, axe for automated testing in CI/CD (Playwright, Cypress, Selenium), and several third-party tools. axe-core is widely regarded as the market leader in automated accessibility testing because it is designed to produce zero false positives by default. When axe-core reports a violation, it is almost always a genuine issue. The engine runs a set of rules corresponding to WCAG success criteria, checks the DOM against each rule, and returns a structured result array with severity (critical, serious, moderate, minor), WCAG conformance references, the specific HTML element involved, and a suggested fix. axe-core catches issues such as missing alt text, low colour contrast, missing form labels, incorrect ARIA attributes, duplicate IDs, and heading hierarchy problems. It is designed to run client-side in the browser or server-side in Node.js test suites.

## Why axe-core? Zero false positives

axe-core's design philosophy is that a testing tool must be trustworthy. False positives waste developer time and erode confidence in the tool. axe-core sacrifices breadth of detection (it will not catch every possible issue) for precision (every issue it reports is real and actionable). This makes it ideal for CI/CD integration, where a false-positive-driven build failure is destructive. Deque reports that axe-core detects approximately 57 percent of all accessibility defects, which combined with manual testing (keyboard, screen reader) yields a comprehensive coverage picture. The engine is also modular: you can include or exclude specific rules.

## Integrating axe-core into your workflow

Browser extension: axe DevTools browser extension for Chrome, Firefox, and Edge provides a one-click analysis within DevTools and is the fastest way to spot-check a page. CI/CD: axe-core integrates with Playwright (@axe-core/playwright), Cypress (cypress-axe), Selenium, and Puppeteer. Run it as part of your end-to-end test suite to catch regressions per commit. CLI: axe-core can also run via the axe-cli npm package for quick command-line scans. Best practice: run axe-core in CI on every PR, use the browser extension during development, and follow up with manual keyboard and screen reader testing before release.

## In code

// axe-core with Playwright
import { test, expect } from '@playwright/test';
import AxeBuilder from '@axe-core/playwright';

test('homepage should have no critical violations', async ({ page }) => {
  await page.goto('https://atomicglue.com');
  const results = await new AxeBuilder({ page }).analyze();
  const critical = results.violations.filter(v => v.impact === 'critical');
  expect(critical.length).toBe(0);
});

## Common questions

Q: Is axe-core the same as axe DevTools?

A: axe-core is the open-source engine. axe DevTools includes axe-core plus a browser extension, a dashboard, and premium features like guided testing and result management. The core engine is free and open source. The DevTools product is Deque's commercial offering.

Q: Does axe-core catch every accessibility issue?

A: No automated tool can. axe-core aims for zero false positives, which means it prioritises accuracy over coverage. It will not catch issues that require human judgment, such as whether alt text is appropriate, whether the focus order is semantically correct, or whether ARIA is used appropriately. Always pair axe-core with manual testing.

## Key takeaways

## Related entries


Last updated July 2026. Permalink: atomicglue.co/glossary/axe-core

Schedule a call

30 min · Video call

1
Date
2
Time
3
Details