Deque • Enterprise software
axe DevTools is the developer-tier accessibility testing platform built on the axe-core engine.
Browser extension, IDE integrations, and CI/CD plugins built on axe-core. The free Chrome extension is the developer entry point. The paid Pro tier adds Intelligent Guided Tests, AI-paired triage, deduplicated reporting, and pipeline gating. Available through Merito with rollout, integration, and audit-program design.
What it is
axe DevTools is the developer-facing tier of the Deque axe portfolio. The free Chrome extension surfaces WCAG findings in the browser during development. The paid Pro tier extends the same engine into IDEs, CI/CD pipelines, and AI coding agents. Both layers run on axe-core, the open-source rules engine that most modern accessibility tooling either embeds directly or implements an overlapping ruleset for.
Pro adds Intelligent Guided Tests (IGTs) for issues that pure automation cannot catch (color contrast judgement calls, focus-order semantics, screen-reader announcement quality), AI-paired triage that deduplicates findings across pages and runs, and CI/CD plugins that gate pull requests on accessibility regressions. Recent additions layer the axe Assistant remediation chatbot on top of findings and the axe MCP Server on top of AI coding agents inside the IDE.
Merito treats Pro plus IGTs plus CI integration as a program-level investment, not a developer toy. The license alone produces no measurable accessibility outcome. The implementation work that does is per-repo CI gating, IGT playbook design for the manual surface, governance for which findings block a PR versus log a warning, and developer training that produces the muscle memory to ship accessible components by default. axe DevTools is the entry point for that program, paired with axe Auditor on the manual side and axe Monitor on the production side.
Ideal use cases
What it is best at
axe-core is embedded in Chrome DevTools, Lighthouse, and many third-party scanners. Findings produced by axe DevTools match the findings developers see across other tools that ship with the same engine. That ruleset consistency is the right reason to consolidate accessibility tooling on Deque.
Pure automated scanning catches roughly half to two-thirds of accessibility issues. IGTs walk a developer through the rest as structured, repeatable manual checks. That coverage gap is where accessibility programs fall apart without a workflow tool.
Cross-page and cross-run deduplication means a single shared header component does not produce 200 identical findings. Triage time stays bounded as the application grows.
First-party plugins for the major pipeline systems mean accessibility gates ship in the same configuration file as security and quality gates. No bespoke wiring required.
axe Assistant explains findings in context and suggests fixes. axe MCP Server brings the same context into AI coding agents inside the IDE. Both compress the developer-feedback loop on accessibility issues from days to minutes.
Core capabilities
Chrome extension surfaces WCAG findings in-page during development, with a 14-day free trial of the full Pro feature set.
Free Chrome extension
800,000+ active installations, basic WCAG scanning, individual-developer use. The widest-deployed accessibility scanner in the developer space.
Pro extension features (14-day trial)
Intelligent Guided Tests, smart configurations, deduplicated cross-page reporting, custom rules, and project-level views. The trial extension is a working preview of the paid tier.
DOM-level findings with element traceback
Each finding points at the exact DOM element responsible, with the WCAG success criterion and a suggested fix. Triage is fast instead of exploratory.
Structured, repeatable manual tests for the WCAG surface that automation cannot fully cover.
Color contrast judgement workflow
Walks a developer through ambiguous color-contrast decisions that automated scoring flags as borderline.
Focus order and keyboard-trap testing
Guided keyboard navigation tests that produce a traceable record of which interactive elements are reachable and in what order.
Screen-reader announcement quality
Structured prompts for verifying that ARIA labels, live regions, and dynamic content updates announce the right thing to assistive technology.
Custom IGT authoring
Teams build their own guided tests for component patterns specific to their design system or compliance scope.
First-party plugins gate pull requests and builds on accessibility regressions across the major CI systems.
Pull request blocking
Configurable severity thresholds determine which findings block a PR merge versus log a warning. Mirrors the security-gate pattern engineering teams already accept.
Build-time scanning
Run axe checks against rendered fixtures, Storybook component matrices, or staging-env URLs as part of the build.
Baseline management
Lock the current accessibility state as a baseline so net-new findings are gated while legacy issues stay in a tracked backlog.
Findings export to issue trackers
Forward findings into Jira, GitHub Issues, GitLab Issues, or Azure Boards as part of the CI run.
Recent additions that bring AI assistance to remediation and IDE workflow.
axe Assistant
AI chatbot that explains findings in context, suggests code fixes, and answers WCAG-interpretation questions. Reduces triage time on ambiguous findings.
axe MCP Server
Model Context Protocol server that exposes axe findings to AI coding agents inside the IDE. Coding agents can read accessibility issues and propose fixes alongside other code-quality signals.
Where it fits in the stack
First-party axe-core SDKs that drop into the test framework the team already runs.
Vendor-documented integration patterns for the major pipeline and source-control systems.
Recent additions exposing axe DevTools findings to AI tooling inside the IDE.
Deployment and implementation
Licensing and packaging
axe DevTools Extension (free)
Browser extension for individual developer use. Basic WCAG scanning in Chrome.
Best for: Individual developers running ad-hoc scans during component development. The widest-deployed entry point.
axe DevTools Pro (14-day trial)
Time-bound trial of the full Pro feature set inside the same browser extension.
Best for: Teams evaluating Pro before contract. Useful as a working preview rather than a feature-stripped demo.
axe DevTools Pro
Paid tier with Intelligent Guided Tests, IDE integrations, CI/CD plugins, project-level views, deduplicated reporting, and the axe Assistant AI chatbot.
Best for: Engineering organizations standing up an accessibility program with CI gating and audit-trail reporting.
Merito services
Pick the engagement that matches where you are in the lifecycle.
WCAG, ADA, and Section 508 program delivery built around the axe DevTools developer tier. Audit playbook design, governance, and ongoing run.
Explore service02License setup, browser extension rollout, CI/CD plugin wiring, IGT playbook design, baseline configuration, and product-team handover.
Explore service03axe DevTools wired into CI/CD so accessibility gates ship alongside security and quality gates in the same pipeline configuration.
Explore service04Front-end developer workshops on axe-core ruleset interpretation, plus test-architect training on CI configuration and IGT design.
Explore service05Named engineer, priority SLAs, and release-time coverage on the axe DevTools rollout and CI gating.
Explore service06Merito-placed engineers experienced with axe DevTools, IGT design, and CI integration on modern web stacks.
Explore serviceaxe DevTools licensing
axe DevTools Pro plus Intelligent Guided Tests plus CI gating, available through Merito with the implementation, IGT playbooks, and developer training that turn the tooling into a compliance program.
Merito point of view
Merito's position. axe DevTools earns its seat fastest when the engineering organization commits to an accessibility program around it. The free extension proves the engine works. The Pro tier produces compliance only when CI gating, IGT playbooks, and developer training are deployed together.
The automation ceiling for accessibility scanning is real. Pure automated scanning catches roughly half to two-thirds of WCAG issues depending on the application surface. Color contrast judgement calls, focus-order semantics, screen-reader announcement quality, and dynamic-content live-region behavior all require structured manual testing. IGTs are the right vehicle for that manual surface inside the developer workflow. axe Auditor is the right vehicle for it inside a structured audit cycle.
Merito recommends starting axe DevTools rollouts with one or two reference repos, where CI gating, IGT playbooks, and developer training all land at the same time. Once that pattern is working, scale across the rest of the engineering org one team at a time. Trying to deploy axe DevTools across 20 repos in week one without playbooks produces 20 noisy CI configurations and zero accessibility outcome.
axe DevTools sits in a four-product stack with axe Linter (pre-commit), axe Auditor (manual), and axe Monitor (production). Most enterprise programs need all four. Customers buying axe DevTools alone get the developer surface; they still need the rest for the full WCAG program.
What buyers usually underestimate
Related from Merito
Related solutions
Related services
Related products
Frequently Asked Questions
Consultation request
Share your engineering team size, repository count, CI host, and current accessibility maturity. A Merito accessibility specialist follows up within one business day.
Pro plus IGTs plus CI
axe DevTools rollouts produce compliance outcomes when the Pro license, IGT playbooks, and CI gating land together. Merito sequences all three as one engagement.
One quadrant of four
axe DevTools is the developer-tier; axe Linter sits left of it at pre-commit; axe Auditor handles the structured manual audit; axe Monitor watches production. Merito scopes the full quadrant set, not just the developer tier.
Next step
A Merito axe DevTools conversation starts with the reference repository, the existing CI configuration, and the developer-training cadence the team can absorb. We scope around the program, not the tool.