axe MCP Server Version 1.3.0 Release Notes

This page is not available in the language you requested. You have been redirected to the English version of the page.
Link to this page copied to clipboard
Not for use with personal data

Release Date

July 1, 2026

Overview

This v1.3.0 release brings the Automated Keyboard Intelligent Guided Test (IGT) to the axe MCP Server through the new igt tool, adds an npm distribution alongside Docker, introduces partial page scans in the analyze tool, and adds batch remediation to the remediate tool.

important

To get this release:

  • Docker — re-pull the image: docker pull dequesystems/axe-mcp-server:latest
  • npm — no separate install step is required; npx runs the latest published version. See Choosing a Distribution.

New Features

igt Tool — Automated Keyboard IGT

The new igt tool runs Deque's Automated Intelligent Guided Tests from your IDE — starting with the Keyboard IGT. Where the axe DevTools Browser Extension normally walks a developer through an IGT with manual prompts, the igt tool drives the test automatically: it tabs through the page, uses AI to analyze each tab stop for focus order and keyboard operability, and returns structured findings a coding agent can act on — no manual fallback steps required.

The response separates confirmed issues from unanalyzedElements (tab stops the AI could not analyze, for manual review), and includes a terminatedReason when a run is cut short — for example, when the test encounters a keyboard trap it cannot escape.

See the igt tool documentation for usage and the full response shape.

npm Distribution

The axe MCP Server can now run as a local Node.js process via npx, in addition to the Docker image. The npm distribution reaches localhost services directly (no Docker host workarounds) and is a good fit if you can't — or prefer not to — run Docker. Because the server drives a real browser, you install a matching Chromium build via Playwright.

See Choosing a Distribution for a side-by-side comparison and setup steps.

Partial Page Scans in the analyze Tool

The analyze tool now accepts an optional selector parameter to scope a scan to a specific region instead of the whole page. Pass a single CSS selector to target an element in the top frame, or an array of selectors to step through iframe and shadow-DOM boundaries. Omit it to scan the whole page exactly as before.

See Partial Page Scans for details and examples.

Batch Remediation in the remediate Tool

The remediate tool now accepts a batch of issues in a single call (up to 25), returning a per-issue result array correlated by a caller-supplied id. Pass all the violations from an analysis together instead of calling the tool once per issue. Credits are still consumed per remediated issue. If you maintain custom agent instructions, update them to send issues as a batch.

See Batch Remediation for the input and output shapes.

Bug Fixes

  • No noteworthy bug fixes in this release

Is this page helpful?

Help us improve this page

Still need help?