Skip to main content

A11yNow MCP

Model Context Protocol (MCP) is an open standard that enables AI applications to connect with data sources as well as external tools and services. A11yNow MCP allows AI assistants to use A11yNow’s accessibility testing capabilities to perform accessibility scans, access compliance with accessibility standards, ask for accessibility advice and guidelines based on WCAG best practices, identify accessibility issues, and generate accessibility reports.

Overview of A11yNow​

A11yNow provides a comprehensive suite of accessibility testing capabilities to help organizations create and maintain accessible digital experiences. The platform combines automated accessibility testing, expert human validation, and actionable reporting to help organizations identify issues, prioritize fixes, and maintain compliance with recognized accessibility standards.

Why Use A11yNow MCP?​

A11yNow MCP brings A11yNow’s accessibility testing capabilities directly into AI-powered development environments. Instead of using separate tools and interfaces, users can perform accessibility testing through their AI assistant using prompts. Benefits of using A11yNow MCP include:

  • Perform accessibility testing directly from your AI assistant
  • Scan websites and applications without switching tools
  • Generate accessibility reports quickly and easily
  • Check compliance with WCAG standards
  • Generate accessibility components and code
  • Fix accessibility issues identified during scans

How does it work?​

A11yNow MCP enables communication between your AI assistant and A11yNow’s accessibility testing tools. The workflow is as follows:

  1. The user asks the AI assistant to perform an accessibility-related task.
  2. The AI assistant determines which A11yNow capability is appropriate.
  3. A11yNow MCP sends the request to A11yNow and returns the results.
  4. The AI assistant presents the results in an easy-to-understand format.

Update the Server​

  1. Check your current version
    Run: npm ls -g a11ynowmcp

  2. Check the newest available on BarrierBreak’s npm registry
    Run: npm view a11ynowmcp version - -registry https://npm.barrierbreak.net

  3. If your MCP server was installed with npm globally:
    Run: npm install -g a11ynowmcp@latest --ignore-scripts –registry https://npm.barrierbreak.net

  4. If you use npx instead and MCP configuration runs something like:
    Run: npx -y a11ynowmcp

  5. To explicitly request the latest version:
    Run: npx -y a11ynowmcp@latest

  6. npx can temporarily use a cached package, to verify if it’s an old version:
    Run: npm cache clean - -force

  7. Then run: npx -y a11ynowmcp@latest

After an update, restart the MCP host so it respawns the server.

  • For Codex CLI/ Opencode – restart the CLI
  • Claude Code - restart the session, or claude mcp remove a11ynow then re-add
  • Claude Desktop / Cursor / VS Code / Windsurf – quit and reopen the app