Skip to content

Free Accessibility Checker

Test any web page for WCAG 2.2 A and AA issues. We load the page in a real Chrome browser and run axe-core, the open-source rules engine behind Lighthouse's accessibility audits. You get a score, the issues that matter most, and how to fix them.

One page per check, 3 free checks a day. No sign-up.

What the checker tests

Each check runs the WCAG 2.2 A and AA rules from axe-core on the page as it looks after loading, at a desktop width of 1280 pixels. It finds problems such as:

  • Text and background colours with too little contrast
  • Images, icons and image buttons with no text alternative
  • Form fields with no label
  • Links and buttons with no accessible name
  • A missing or wrong page language
  • ARIA roles and attributes used in ways that break assistive technology
  • Heading, list, table and landmark structure
  • Touch targets smaller than WCAG 2.2 allows (2.5.8 Target Size)

What automated checks miss

Automated rules find a lot, but not everything. In Deque's study of real audits, automated testing found 57% of accessibility issues by volume. The rest need a person. After you fix what the checker finds, test these by hand:

  • Can you reach and use everything with only a keyboard, in a sensible order, with a visible focus?
  • Does a screen reader announce changes, errors and dialogs?
  • Does each image description say what matters, not just that an image is there?
  • Do videos have captions, and does the page still work zoomed to 400%?
  • Are instructions and error messages clear enough to act on?

Read more in automated vs manual accessibility testing and the WCAG 2.2 checklist.

Check every page, on every deploy

The free checker tests one page at a time. With a free API key (25 scans a month, no card) you can scan whole sites, get every issue and element, and fail a build when new issues appear.

From the command line

export A11YFLOW_API_KEY=sk_live_your_key
npx @a11yflowdev/cli scan https://example.com --fail-on serious

With the REST API

curl -X POST https://api.a11yflow.dev/v1/scans \
  -H "Authorization: Bearer sk_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com"}'

From your AI coding assistant (MCP)

{
  "mcpServers": {
    "a11yflow": {
      "command": "npx",
      "args": ["@a11yflowdev/mcp"],
      "env": { "A11YFLOW_API_KEY": "sk_live_your_key" }
    }
  }
}
Get a free API keyRead the API docs

Questions

Is the checker really free?
Yes. You can run 3 checks a day with no account. For more, a free API key gives you 25 scans a month with full reports, and no card is needed.
Which standard does it test against?
WCAG 2.2 at levels A and AA. It runs the axe-core rules tagged for WCAG 2.0, 2.1 and 2.2 A and AA, including the target size rule that axe-core leaves off by default.
Can it check a page behind a login?
No. It sees the page the way a logged-out visitor does. Pages that need a login, or that block automated browsers, cannot be checked here.
Do you keep the address and the result?
Yes. We keep the address and the result so a link to it keeps working and so we can stop abuse. To count checks, we keep a scrambled (hashed) form of your IP address for 2 days. Privacy policy.
Does a score of 100 mean my page is accessible?
No. A score of 100 means no automated rule failed. Automated rules cannot judge everything WCAG asks for, so a person still needs to test with a keyboard and a screen reader.