axe MCP Server Version 1.2.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

June 3, 2026

Overview

This v1.2.0 release adds support for browser interactions before scanning via the analyze tool's new before array, introduces OAuth 2.0 authentication as an alternative to static API keys, and includes minor bug fixes.

important

To get this new release, you must re-pull the Docker image:

docker pull dequesystems/axe-mcp-server:latest

New Features

Browser Interactions Before Scanning

The analyze tool now supports an optional before array of interaction steps that run after the page loads but before the accessibility scan. This unlocks real-world testing scenarios such as:

  • Login-gated pages — fill in credentials and submit before scanning the post-login page
  • Cookie banners and overlays — dismiss consent dialogs and modals so they don't block the scan
  • Dynamic content — wait for client-rendered content to appear before scanning

See the Browser Interactions Before Scanning documentation for the full list of supported actions and examples.

OAuth 2.0 Authentication

You can now authenticate to the axe MCP Server by signing in with your axe Account instead of using a static API key. The new @deque/axe-auth CLI handles the OAuth 2.0 Authorization Code Flow (with PKCE), stores tokens securely in your OS keychain, and silently refreshes them so you stay signed in. The server accepts OAuth access tokens alongside existing API key authentication, so current API key setups continue to work unchanged.

See the OAuth 2.0 Authentication documentation for setup instructions, IDE configuration, and the full axe-auth command reference.

Bug Fixes

  • Minor bug fixes

Is this page helpful?

Help us improve this page

Still need help?