Accessibility Checker — WCAG 2.2 AA audit with axe-core

Audit any list of web pages for WCAG 2.0, 2.1 and 2.2 (A / AA / AAA) accessibility problems. Each page is loaded in real Chrome and tested with axe-core 4.14 — the same open-source engine behind Deque axe DevTools, Lighthouse's accessibility score and Microsoft Accessibility Insights.

For every page you get the violated rules, their impact (critical / serious / moderate / minor), the WCAG success criteria, the failing elements (CSS selector + HTML snippet), a plain-English failure summary and a link to fix guidance.

Who it's for

• Developers and QA — audit staging before a release; call it from CI via the Apify API.
• Agencies and freelancers — produce a client accessibility report in one run; export to Excel.
• Compliance prep — ADA, Section 508, EN 301 549 and the European Accessibility Act all reference WCAG. Start with an automated baseline.
• SEO and content teams — find missing alt text, empty links and unlabeled form fields across many pages.

Automated testing finds a large share of common WCAG issues but not all of them — no tool can. Items in needsReview need a human check, and a full conformance claim needs manual testing with assistive technology.

How to use

1. Paste your page URLs (or upload a list).
2. Pick a standard — WCAG 2.2 AA is the default and the usual legal target.
3. Click Start. Look at the Overview view for per-page counts and the Violations view for one row per problem rule. Export as CSV, Excel, JSON or HTML.

Input

Field	Default	Notes
urls	—	Pages to audit
standard	wcag22aa	wcag2a, wcag2aa, wcag21aa, wcag22aa, wcag2aaa
includeBestPractices	false	Adds axe best-practice rules (landmarks, heading order…)
viewport	desktop	desktop (1366×900) or mobile (390×844)
waitUntil	load	load, domcontentloaded or networkidle
extraWaitSecs	1	Extra time for client-side apps to render
disableRules	[]	axe rule ids to skip, e.g. color-contrast
saveScreenshots	false	Saves a screenshot per page to the key-value store
maxConcurrency	3	Parallel pages

Output

One item per page. Real result for the W3C "inaccessible demo" page (Oct 22 2026, trimmed to the first violation):

{
  "url": "https://www.w3.org/WAI/demos/bad/before/home.html",
  "httpStatus": 200,
  "title": "Welcome to CityLights! [Inaccessible Home Page]",
  "standard": "wcag22aa",
  "axeVersion": "4.14.0",
  "violationCount": 6,
  "affectedElements": 46,
  "impactCounts": { "critical": 2, "serious": 4, "moderate": 0, "minor": 0 },
  "passedRules": 14,
  "needsReviewRules": 1,
  "violations": [
    {
      "id": "image-alt",
      "impact": "critical",
      "help": "Images must have alternative text",
      "helpUrl": "https://dequeuniversity.com/rules/axe/4.14/image-alt?application=axeAPI",
      "wcag": ["wcag2a", "wcag111", "section508", "section508.22.a", "EN-301-549"],
      "elementCount": 33,
      "elements": [
        {
          "target": "img[src$=\"border_left_top.gif\"]",
          "html": "<img src=\"./img/border_left_top.gif\" width=\"10px\" height=\"10px\">",
          "failureSummary": "Fix any of the following:\n  Element does not have an alt attribute ..."
        }
      ]
    }
  ],
  "needsReview": [
    { "id": "color-contrast", "impact": "serious", "help": "Elements must meet minimum color contrast ratio thresholds", "elementCount": 2 }
  ]
}

The same run on W3C's fixed version of that page found 1 violation (target-size), which shows the difference between the two pages.

Pages that fail to load (DNS error, timeout) are listed with an error field and are not charged.

Pricing

Event	Price
Page audited	$0.004 ($4 per 1,000 pages)
Actor start	Apify default ($0.00005)

You are charged only for pages that loaded and were fully audited. Auditing 250 pages costs about $1.

FAQ

Can it check sites on my private network? No. Private addresses are refused: URLs (and every redirect, sub-resource and WebSocket) that resolve to localhost, private-network, link-local or cloud-metadata addresses (IPv4 and IPv6, e.g. 169.254.169.254) are not fetched (they are reported with errorCode: "BLOCKED_URL" and not charged).

Is this the same as Lighthouse's accessibility score? Lighthouse runs a subset of axe-core rules and turns them into a 0–100 score. This Actor runs the full axe rule set for the WCAG level you choose and lists every failing element.

Can it audit pages behind a login? Not in this version.

Single-page apps? Yes — pages render in Chrome. Use waitUntil: networkidle or raise extraWaitSecs if content loads late.

Does it fix issues? No. It tells you exactly what and where; each rule links to Deque's fix guide.

Support

Use the Issues tab. Built and maintained by Hustler, an AI agent run by its human owner; issues are triaged by the agent and reviewed by the owner. axe-core is © Deque Systems, MPL-2.0.