Website Accessibility Checker (WCAG 2.1 AA)

Check any website for accessibility problems in a real Chrome browser and get a clear report per page: a score out of 100, how many issues of each severity, and every issue explained in plain English with how to fix it. Built on the axe-core rules engine used by most professional accessibility auditors.

Use it to check your own site, audit client sites, monitor a portfolio of stores, or find businesses whose sites need accessibility work.

Why it matters

• ADA (United States): thousands of website accessibility lawsuits are filed every year, most against online stores.
• AODA (Ontario, Canada): organizations with 50+ employees must make their public websites meet WCAG 2.0 AA.
• European Accessibility Act: applies to e-commerce sites selling to EU consumers since June 2025.

All three point to WCAG AA, which is what this checker tests by default.

What you get for each page

Field	Example
score	72 (out of 100; weighted by severity and how many elements are affected)
critical / serious / moderate / minor	1 / 3 / 1 / 0 issue types
totalIssues	46 affected elements
topIssue	Text that is too faint (31)
violations	Full list, worst first: title, why it matters, how to fix, WCAG criteria, affected element count, example selectors and HTML
passedChecks, needsManualReview	Rules that passed, and rules that need a human to confirm

Example issue:

{
  "id": "link-name",
  "impact": "serious",
  "title": "Links and icons with no name",
  "whyItMatters": "A screen reader announces these as just \"link\", so visitors can't tell where they go (often the cart, search or social icons).",
  "howToFix": "Give each icon link a hidden label, e.g. add aria-label=\"Cart\" to the <a> tag, or alt text to the image inside it.",
  "wcag": ["2.4.4", "4.1.2"],
  "affectedElements": 4,
  "examples": [{ "selector": "a.header__icon--cart", "html": "<a href=\"/cart\" class=\"header__icon--cart\">..." }]
}

How to use

1. Paste one or more URLs into Pages or sites to check.
2. Leave Pages per site at 1 to check just those pages, or raise it (e.g. 10) to also check linked pages on the same site such as collections, product pages and contact.
3. Pick a standard (WCAG 2.1 AA is recommended) and run.
4. Open the Overview table for scores at a glance, or export JSON/CSV/Excel for the full issue lists.

Tip: for many sites at once, put one home page per site in the list and keep Pages per site small.

Pricing

$10 per 1,000 pages checked ($0.01 per page). Pages that fail to load are not charged. Set a maximum cost per run and the checker stops when it is reached.

Limits and notes

• Automated checks find roughly a third to a half of WCAG issues. Things like keyboard order, captions and meaningful alt text still need a human review; needsManualReview lists the rules that could not be decided automatically.
• Pages behind logins, carts and checkouts are skipped when following links.
• Some sites block automated browsers; those pages return an error row and are not charged.

FAQ

Is a score of 100 a guarantee of compliance? No. It means no automated rule failed. Use the report to fix the bulk of issues quickly, then review the rest manually.

Can I check mobile layouts? Yes, turn on Check mobile layout.

Can I run it on a schedule? Yes. Save it as a task and schedule it daily or weekly to catch regressions after theme or content changes.