axe DevTools review

Axe DevTools is Deque’s automated accessibility testing product for web, mobile and test workflows. Deque’s homepage says it can find and fix up to 80% of accessibility issues; that is the company’s claim, not a promise that a scan catches everything. The product is aimed at finding issues and helping teams address them, rather than replacing accessibility review across a whole product.

The entry point is the free Chrome extension, which the pricing page describes as page-by-page testing: one page at a time. The Pro extension costs $60 per user per month, includes one user per license and offers a 14-day trial without a credit card. Teams can ask about the Web Bundle, but its price is custom and requires a demo or sales contact. Annual prices are not published. So the practical choice is between limited individual checks and a team purchase whose cost you need to confirm with Deque.

Axe DevTools makes sense when developers need to identify accessibility issues during web work and then fix them in the code. Deque says the product supports web, mobile and test stacks, giving teams more than a one-off browser audit as a possible workflow. The free extension is a low-commitment way to check individual pages before deciding whether a paid license or bundle is warranted.

• The free extension provides automated checks one page at a time, which suits focused spot checks without an initial subscription.
• Pro adds a setting to select an accessibility standard, according to a Reddit commenter. That may matter to teams that need to focus scans on a particular conformance target.
• A developer in one Reddit thread liked the ability to test end-to-end flows and multi-state pages or components, including modals and popups. That is a user report, not a published plan guarantee.
• The Web Bundle includes the Axe MCP Server at no additional cost, according to the published pricing details. For teams already evaluating that bundle, this avoids a separately listed MCP charge.

The main appeal is fitting checks into development work. It is less compelling if you only need occasional page-level scans and can use the free extension.

The pricing changes the value calculation quickly. Pro is $60 per user per month, with one user per license; annual pricing is not published. The free extension has no published seat limit, while the Web Bundle has custom pricing and no published usage or seat limits. The amount of monthly AI credits in Pro is also not published. Ask Deque for the bundle’s full cost and limits before moving a team onto it.

Automation also does not remove the need to interpret findings in context. In one Reddit thread, a developer described difficulty applying HTML-oriented diagnoses to React components, including list structure and heading issues. Another commenter suggested alternatives such as jest-axe with the free axe-core library for component tests. In a separate thread, a free-extension user was confused by AAA results; a commenter said standard selection is available in Pro. These are user reports, not proof that every team will hit the same problems, but they point to a real decision: check whether the free version’s controls and page-by-page scope fit your workflow before paying per developer.

The free Axe DevTools Extension covers automated checks on one page at a time. Its seat limit is not published. The Pro extension costs $60 per user per month, with one user per license, monthly AI credits (the amount is not published) and a 14-day trial that does not require a credit card. That is a clear jump from free if several developers need licenses: three Pro users would cost $180 per month, before any unpublished costs.

The Web Bundle has custom pricing; Deque requires a demo or sales contact for a quote. It includes the Axe MCP Server at no additional cost, but bundle usage and seat limits are not published. Other add-on and overage costs are also not published. Annual pricing is not published for either paid option, so we can’t compare monthly billing with an annual commitment. Before budgeting, confirm the bundle’s user limits and any costs beyond the included MCP Server. The free extension is the straightforward fit for page-by-page checks; team pricing needs a sales conversation.

The published product information does not document a migration process, data-export options, or how results move between Axe DevTools and another testing tool. Those details are worth confirming with Deque before you switch, especially if your team needs to retain historical findings or connect checks to existing test workflows. The Web Bundle is described as supporting teams, but its usage and seat limits are not published.

We also don’t have Reddit posts or comments in the published material, so we can’t attribute reasons for leaving to users there. The practical cost question is clearer: Pro is priced per user, while the team bundle requires a sales quote. Count the developers who need Pro access, then ask Deque about exports, workflow coverage, bundle limits and any fees beyond the included MCP Server. If you’re leaving, check whether your current tool can export findings and whether your team can keep or recreate its existing checks; the published sources don’t establish that Axe DevTools offers those capabilities.