nexaaly-a11y

Check whether real people can actually use a web page — from your agent.

Runs a real browser against one page and reports accessibility problems with the code that fixes each one. Free.

"Check nexaaly.com for accessibility problems"
"Can keyboard users complete the checkout on example-shop.dk?"
"Does this page meet WCAG 2.1 AA?"

What it finds that standard scanners don't

Almost every free accessibility checker runs axe-core. It is good software and it is inside this tool too. But a rules engine over the accessibility tree cannot see some of the failures that matter most.

The Dutch regulator (ACM) publishes what it most often finds wrong in webshops. Against that list:

The one that matters most looks like this:

<div class="buy" onclick="addToCart()">Add to cart</div>

Styled like a button, works with a mouse, not in the tab order and deaf to Enter and Space. axe scores that page as passing its keyboard checks.

We found controls with exactly this defect on 4 of 27 Danish and Swedish webshops — roughly one in seven.

What we did not find, and will not claim: none of those four was the add-to-cart button. They were a shipping-country selector, two icon buttons, a "show details" link and a section wrapper. Each is a genuine WCAG 2.1.1 failure that locks out keyboard users — but we did not test a checkout, so we cannot say a purchase was blocked. The risk is that the same defect on the same template lands on the buy button. That is a risk, not a measurement.

Install

Requires Node 20+. Chromium is downloaded by Playwright, or set CHROMIUM_PATH to use a system one (needed on ARM).

// claude_desktop_config.json / .mcp.json
{
  "mcpServers": {
    "nexaaly-a11y": {
      "command": "node",
      "args": ["/path/to/mcp-a11y/server.mjs"]
    }
  }
}

git clone https://github.com/AccessNexaaly/nexaaly-a11y.git
cd nexaaly-a11y && npm install
claude mcp add nexaaly-a11y -- node "$PWD/server.mjs"

Or use the hosted one, with no install at all

claude mcp add --transport http nexaaly-a11y https://nexaaly.com/mcp

The hosted endpoint cannot reach localhost, since your dev server is behind your firewall. Run it locally for that; the checks are identical.

Tool

check_accessibility(url) — one page, read-only, ~20 seconds. A bare domain works (example.com). Prefer a product or checkout page; that is where accessibility failures cost sales.

Returns a summary, each finding with its WCAG criterion and a copy-pasteable fix, and — if the page looks like a shop — the cart URL worth checking next.

Honest limits

• Automated testing finds roughly a quarter to a half of WCAG issues. This tool included.
• It cannot tell you whether you comply with anything. No tool can. Anyone selling certainty from a scan is selling you something they do not have.
• On 27 real sites, axe-core alone found 92% of the issues by count. The 8% it missed is where the checkout breaks — but if you are not running any scanner, run axe-core first, for free.
• One page per call. No crawling, no login, nothing stored beyond the URL and the result.

The 30-second test that needs no tool

Open your own checkout and try to complete a purchase using only Tab, Enter and Space. Most people who try it are surprised.

Built by Nexaaly (CVR 40643419), who fix these and send the change as a pull request rather than a report. The tool is free and stays free.

Method and full data: [nexaaly.com/nordic-webshop-accessibility-2026](https://nexaaly.com/nordic-webshop-accessibility-2

... View full README on GitHub