Reported issues for io.github.JustasMonkev/mcp-accessibility-scanner

Pod holds 10 of 10 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to io.github.JustasMonkev/mcp-accessibility-scanner.

Most discussed

`browser_evaluate` throws `_evaluateFunction is not a function` on every call (removed in playwright-core 1.59)

Small bug report: browser_evaluate throws on every call (page- and element-scoped alike) with receiver._evaluateFunction is not a function. The other tools (browser_navigate, browser_take_screenshot, browser_snapshot, ...) all work fine.

Root cause

src/tools/evaluate.ts:

const receiver = locator ?? tab.page as any;
const result = await receiver._evaluateFunction(params.function);

Upstream Playwright removed _evaluateFunction from playwright-core's client API

Read the thread · 2026-06-19 · closed · external user · 2 comments

Feature Request : Integrate a Prometheus client into the accessibility scanner MCP server to track usage metrics

Objective To implement a Prometheus client within the mcp-accessibility-scanner to enable the collection, monitoring, and visualization of tool performance and usage statistics.

Problem Statement Currently, the MCP accessibility scanner operates as a black box. Maintainers and users lack real-time visibility into:

How many accessibility scans are being performed.

Which URLs or components are being scanned most frequently.

The latency/performance of the underlying accessibility engine

Read the thread · 2026-04-20 · closed · external user · 1 comment

Feature Request: Implement Streaming Support for Accessibility Scans

Problem Description Currently, the mcp-accessibility-scanner appears to operate using a standard request-response pattern. For complex pages or deep scans, this can lead to:

Timeouts: Large pages may exceed the default MCP/JSON-RPC timeout limits.

Poor UX: The user (and the LLM) receives no feedback until the entire process is complete.

Proposed Solution I suggest updating the server to support streaming. By leveraging the MCP sampling or progress notifications, the server could emit results

Read the thread · 2026-03-04 · closed · external user · 1 comment

[Feature Request] Add Docker support for containerized deployment

Currently, the repository requires a local environment setup to run the MCP server. While this works for local development, it can lead to issues and make it difficult to deploy the server in cloud environments or via orchestration tools. I would like to propose adding a Dockerfile to the project to streamline the setup process.

Proposed Changes :

I am happy to submit a Pull Request for this. My plan is to:

Create a multi-stage Dockerfile to keep the final image size small.
Add a .dockeri

Read the thread · 2026-02-27 · closed · external user · 2 comments

Is there any paramters to help to control playwright.

Hi. Still use this MCP in langGraph with react Agent to do the web accessibility test.

Always get exceptions like:

I just wondering if it's possible to provide some parameter to control playwright. Like the timeout for waiting or navigating. Or enable headerless mode and other functions.

Thank you.

Read the thread · 2025-09-25 · closed · external user · 2 comments

When use broswer_type tool get error.

When I use the MCP in LangGraph. And provide user message like: "Navigate to xxx with browser_navigate; Use browser_wait_for to wait for "登陆" button to appear; Type xxxx with browser_type，Type xxx with browser_type,Click “登陆” botton using browser_click; Use browser_wait_for "xxxx" text to appear，Take a browser_snapshot, Run scan_page with violationsTag: ["wcag21aa"]." And it always failed as: ToolMessage(content="Error: ToolException('TypeError: locator._generateLocatorString is not a function')

Read the thread · 2025-09-16 · closed · external user · 1 comment

Can we support Authenticated Login in this MCP Server

I'll give url, username and password and want to capture all url's and scan each page and return results. Can we add this enhancement ?

Read the thread · 2025-05-19 · closed · external user · 3 comments

Glama listing is missing Dockerfile

Your MCP server is currently listed on the Glama MCP directory, but it is not available for others to use because it does not have a Dockerfile.

It takes only a few minutes to fix this:

Go to your server's listing: JustasMonkev/mcp-accessibility-scanner
Click "Claim" to verify ownership.
Once claimed, navigate to the [admin Dockerfile page](ht

Read the thread · 2025-04-20 · closed · external user · 1 comment

Most recent

audit_screen_reader reports missing-accessible-name on links and buttons whose text is in a child element

Ran audit_screen_reader on a site I maintain and got 14 missing-accessible-name hits on links that are clearly named. Boiled it down to this:

<a href="/docs"><strong>Docs</strong></a>
<button><span>Save</span></button>

Both get reported as "exposes no accessible name". Chrome's own accessibility tree names the link "Docs", and a plain page.ariaSnapshot() prints - link "Docs". VoiceOver reads them fine.

What's going on: the tool uses ariaSnapshot({ mode: 'ai' }), and since

Read the thread · 2026-08-29 · closed · outside contributor · 0 comments

ERR_MODULE_NOT_FOUND

After I installed the server. Once I tried to start it will got failed like below: `$ npx mcp-accessibility-scanner node:internal/modules/esm/resolve:265 throw new ERR_MODULE_NOT_FOUND( ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find module 'D:\software\nodejs\node_cache_npx\03d14fe5aa9b614e\node_modules\mcp-accessibility-scanner\lib\program.js' imported from D:\software\nodejs\node_cache_npx\03d14fe5aa9b614e\node_modules\mcp-accessibility-scanner\cli.js at finalizeResoluti

Read the thread · 2025-09-13 · closed · external user · 1 comment

The remaining reports are on the project's issue tracker.