Free accessibility checker

Paste a URL. We load the page in a real browser, run axe-core against it, and list what fails WCAG 2.2 AA — grouped by how much it matters, with the elements responsible. No account, no card, no extension.

What it checks

The rules that make up WCAG 2.0, 2.1 and 2.2 at levels A and AA — the levels almost every accessibility policy and procurement requirement actually names. Colour contrast, form labels, image alternatives, heading order, landmark structure, link purpose, ARIA validity.

It deliberately does not run axe's best-practice rules. Those flag things that are worth fixing but are not WCAG failures, and a tool that reports 47 problems where the standard says 9 teaches you the wrong thing about your site.

What it cannot tell you

Automated testing finds somewhere around a third of accessibility problems. That is a genuinely useful third — contrast and missing labels are common, mechanical and everywhere — but no checker, this one included, can tell you whether your alt text is accurate, whether your tab order makes sense, or whether a screen reader user can complete your checkout.

A clean report here means the machine-checkable rules pass. It does not mean the page is accessible. Anyone selling you a tool that claims otherwise is selling you a compliance risk.

Limits, stated plainly

When you want the API instead

This page is one page, once. POST /v1/audit is the same engine with the parts a build needs: any viewport, your own rule tags, an optional screenshot, the full node list, and a response you can fail CI on. 

curl -X POST https://api.getsnap.dev/v1/audit \
  -H "X-API-Key: sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com","tags":["wcag22aa"]}'

A free key is 100 runs a month, no card. Get one, or read the API reference.

Frequently asked questions

Is this really free?

Yes. No account, no card, no email. Six runs an hour per visitor, with a shared daily limit across everyone. Runs that fail do not count against you.

Does a clean result mean my site is accessible?

No. It means the automatically checkable rules pass, which is roughly a third of what accessibility covers. The rest needs a person, ideally one who uses assistive technology.

Which standard does it test against?

WCAG 2.0, 2.1 and 2.2 at levels A and AA, plus the Section 508 overlap. AAA rules are not included; almost nothing is required to meet AAA in full.

Can I check a page behind a login?

Not with the free tool, which only loads public pages. The API supports cookies and custom headers for authenticated pages.

Why do I get different results from my browser extension?

Extensions test the page as your browser rendered it, after your extensions, your cookies and your viewport. This runs a clean headless Chromium at a fixed 1280×720. Differences usually come from content that varies by session.