Skip to main content

Troubleshooting

Common Installation and Configuration Issues

  1. Chromium missing or "browser not found" during a scan.
    A11yNow uses Playwright to open webpages for scanning. The required Chromium browser must be installed separately.

Run: npx playwright install chromium

  1. Installation fails with fsevents / node-gyp rebuild or binding.gyp not found.
    If the A11yNow installation fails with error related to fsevents, node-gyp, or binding.gyp, use the following installation command:

Run: npm install -g a11ynowmcp --ignore-scripts --registry https://npm.barrierbreak.net

The --ignore-scripts option instructs npm not to run package installation scripts.

  1. a11ynowmcp: command not found in an MCP host
    If A11yNow works from your terminal but your AI assistant or MCP host cannot find a11ynowmcp, the MCP host may not be using the same PATH environment as your terminal.

Run the following command to find the location of the executable: which a11ynowmcp

Alternatively, if the MCP host supports npx, configure it as follows:
command: "npx", args: ["-y", "a11ynowmcp"]

This allows the MCP host to run A11yNow through npx instead of relying on the globally installed executable being available in the system PATH.