MCP server

MCP Accessibility Scanner: axe Audits for AI Agents

MCP Accessibility Scanner lets an AI coding agent run axe-core checks, test keyboard focus and save findings for review, all inside a browser it controls.

Run
npm install -g mcp-accessibility-scanner --allow-scripts=re2
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is MCP Accessibility Scanner?

MCP Accessibility Scanner is an MCP server by JustasMonkev that runs axe-core accessibility audits in a real browser. Its tools scan a page, crawl a site, test keyboard focus, inspect names for screen readers and check text spacing. The README says automated checks do not certify WCAG compliance.

It is an MCP server that lets a coding agent inspect a page, run axe checks, exercise keyboard focus and save findings. The README summarizes it as accessibility checks inside your coding agent: axe scans, keyboard-focus checks and repeatable reports.

It also includes browser automation tools such as navigate, click, type and screenshot, so the agent can reach the state of the page it needs to test, then scan it.

What it changes in your workflow

  • The agent scans the page it just edited and gets axe violations with remediation links, plus an optional annotated screenshot.
  • audit_site crawls internal pages and writes a JSON report that aggregates violations across the site.
  • audit_keyboard presses Tab and checks skip links, focus visibility, focus traps, target size and obscured focus.
  • scan_page_matrix reruns axe across variants such as mobile, forced colors, reduced motion and 200 percent zoom.

Local setup at a glance

MCP Accessibility Scanner
Where it runsOn your machine as the mcp-accessibility-scanner command
Transportstdio
Installnpm install -g mcp-accessibility-scanner --allow-scripts=re2
BrowserGoogle Chrome must be installed first
OutputReports and screenshots go to a folder set with --output-dir

Who it is for

Best for

  • Developers who want axe findings inside the agent loop while they fix a page.
  • Teams auditing a whole site or pages behind a login, using a stored session.
  • Reviews that need repeatable JSON reports to compare before and after a fix.

Not for

  • Proof of WCAG compliance. The README says automated checks do not certify it and manual testing is still needed.
  • Real screen reader testing. The audit_screen_reader tool inspects the accessibility tree; it drives no actual screen reader.
  • A one-line install. It needs Chrome and a native dependency; see the A11y Ally skill for a lighter skill route.

Use it with UiChemy

Scan pages you built with UiChemy before launch. Composer writes HTML, CSS and JS for Elementor or Gutenberg, so the scanner can open the live URL and report issues you then fix in the editor. Click Get Started on uichemy.com. For wording and fixes, see the accessibility audit skill.