Accessibility Audit — Whole Site, WCAG 2.1 AA

Crawl an entire website and check every page for accessibility problems against WCAG 2.1 level A and AA. For each page you get a score, the specific violations with the elements that fail and how to fix them, and — the part that saves you the most time — a site-wide ranking of which rules break the most pages, so you fix one component or template and clear the issue everywhere.

Runs on demand, on a schedule, or from the API. No setup, no API keys.

Why this one

• A real browser on every page. Each page is rendered in Chromium and checked with axe-core, the engine used by most accessibility tools. Dynamic content, ARIA state and computed colours are all checked, not just the raw HTML.
• Shows what to fix first across the whole site: a ranking of which rules fail on the most pages, so you fix one template and clear the issue everywhere.
• Developer-ready detail: the failing elements' CSS selectors, impact level, WCAG criteria and a link to the fix guide for every violation.
• Never loses a run. On a big site it stops before the timeout and still writes the full summary for the pages it finished.
• Pick your standard: WCAG 2.1 A/AA plus best practices by default, or any set of axe tags.

What you get

Per page (dataset row):

{
  "url": "https://example.com/pricing",
  "score": 76,
  "hasViolations": true,
  "counts": { "critical": 0, "serious": 3, "moderate": 7, "minor": 2 },
  "passes": 84,
  "violations": [
    { "id": "color-contrast", "impact": "serious",
      "help": "Elements must meet minimum contrast ratio thresholds",
      "helpUrl": "https://...", "wcagTags": ["wcag2aa", "wcag143"],
      "targets": ["main > .card:nth-child(2) > a"] }
  ]
}

Whole site (SUMMARY in the key-value store):

{
  "pagesScanned": 54,
  "pagesWithViolations": 21,
  "criticalViolations": 2,
  "seriousViolations": 28,
  "mostCommonRules": [
    { "rule": "color-contrast", "affectedPages": 14 },
    { "rule": "link-name", "affectedPages": 9 }
  ]
}

Input

{ "startUrls": [{ "url": "https://example.com" }], "crawl": true, "maxPages": 100 }

Optionally restrict to specific WCAG rule tags, cap the crawl, or exclude URL patterns.

Use it for

• A full-site accessibility audit before a compliance deadline (EAA, ADA, Section 508)
• Prioritising remediation work by impact and reach
• Regression testing in CI — fail the build if new critical issues appear
• Auditing many client sites from the API

How it works

Each page is opened in a real browser and evaluated with an industry-standard rules engine, so dynamic content, ARIA state and computed styles are all checked — not just the raw HTML.

Browser scans are slow (a few seconds per page). The Actor watches its own run timeout and stops crawling ~45s before it, then still writes the full summary and report from the pages it finished — the run ends SUCCEEDED with stoppedEarly: true rather than being killed with no output. For a complete large-site audit, raise the run Timeout (Input → Run options) or lower maxPages.

Pricing

Pay per page scanned in a real browser. Pages that fail to load are free.

Event	Price
Page scanned	$0.01
Run start	$0.00005

Examples: a 100-page site costs about $1.00. 500 pages cost about $5.00.

Run it from the API, a schedule or an automation

Run it on demand, schedule it in Apify Console → Schedules (e.g. weekly), or call it from code, n8n, Make or Zapier. One synchronous call returns the rows:

curl -X POST "https://api.apify.com/v2/acts/moonweil~accessibility-scanner/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"startUrls":[{"url":"https://example.com"}],"crawl":true,"maxPages":100}'

Add a webhook or Slack / email integration on Run succeeded to get the results pushed to you.

FAQ

Does a clean report mean my site is compliant? No automated tool can certify WCAG, EAA or ADA compliance. Automated checks catch a large share of common issues (contrast, names, labels, ARIA), but things like keyboard flow and meaningful alt text still need a human review.

Which standard does it test? WCAG 2.1 level A and AA plus axe best practices by default. Change runOnlyTags to narrow or widen it.

How long does it take? A few seconds per page. For large sites, raise the run timeout or lower maxPages. If time runs out, you still get the summary for every finished page.

Can it fail my CI build? Yes. Run it from the API and fail on any critical violation or on a score below your threshold.