โ™ฟ WCAG 2.2 Accessibility Auditor โ€” Bulk axe-core avatar

โ™ฟ WCAG 2.2 Accessibility Auditor โ€” Bulk axe-core

Pricing

from $10.00 / 1,000 url auditeds

Go to Apify Store
โ™ฟ WCAG 2.2 Accessibility Auditor โ€” Bulk axe-core

โ™ฟ WCAG 2.2 Accessibility Auditor โ€” Bulk axe-core

Bulk WCAG 2.2 accessibility auditor. Render sites with Chrome, scan with axe-core, return violations, severity, and score.

Pricing

from $10.00 / 1,000 url auditeds

Rating

0.0

(0)

Developer

Stephan Corbeil

Stephan Corbeil

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

14 days ago

Last modified

Share

Audit any website for WCAG 2.2 AA compliance in seconds. Headless Chrome renders each page, axe-core scans for violations, and you get a structured report per URL โ€” severity, WCAG tags, failing selectors, HTML snippets, and a 0-100 accessibility score.

Why this exists: Enterprise accessibility platforms (Siteimprove, AudioEye, Monsido, Deque axe DevTools Pro) charge $5kโ€“$100k/year for site-wide audits. The open-source axe-core engine they all use under the hood is free and MPL-licensed. This actor wraps axe-core in a headless Chrome runner with a clean JSON output โ€” so devs, agencies, and SMBs can audit hundreds of pages for cents, then fix issues without paying for a dashboard they'll check twice a year.

๐Ÿ”‘ Features

  • WCAG 2.2 AA by default โ€” includes wcag2a, wcag2aa, wcag21aa, wcag22aa tag sets
  • axe-core 4.10.0 โ€” same engine used by Deque, Microsoft Accessibility Insights, Google Lighthouse
  • Bulk mode โ€” audit 100 URLs in one run, pay per URL audited
  • Severity breakdown โ€” critical / serious / moderate / minor counts per page
  • Top-25 failing rules โ€” with CSS selector, HTML snippet, and human-readable failure summary
  • 0-100 accessibility score โ€” severity-weighted, deterministic, comparable across runs
  • Real browser rendering โ€” catches client-side React / Vue / Angular issues that static HTML scanners miss
  • Custom WCAG tag config โ€” audit against 2.0, 2.1, 2.2, or best-practice only

๐Ÿ’ผ Common Use Cases

  • Legal compliance โ€” ADA, EN 301 549, Section 508 spot-checks before launch
  • Agencies & consultancies โ€” white-label audits for client sites at bulk pricing
  • CI/CD gating โ€” fail builds on critical WCAG violations
  • Pre-redesign baseline โ€” scan the current site before a redesign, track improvement
  • SEO audits โ€” accessibility overlaps with SEO (alt text, heading structure, link labels)
  • Procurement โ€” audit vendor SaaS tools you're evaluating for a11y compliance
  • Lawsuit risk reduction โ€” screen for low-hanging a11y issues that drive serial-plaintiff demand letters

๐Ÿ“ฅ Input Example

{
"urls": [
"https://example.com/",
"https://example.com/products",
"https://example.com/checkout"
],
"wcagTags": ["wcag2a", "wcag2aa", "wcag22aa"],
"timeoutMs": 25000
}

๐Ÿ“ค Output (per URL)

{
"url": "https://example.com/",
"audit_engine": "axe-core 4.10.0",
"wcag_version": "2.2",
"total_violations": 7,
"total_passes": 38,
"total_incomplete": 2,
"total_inapplicable": 62,
"severity_breakdown": {
"critical": 1,
"serious": 3,
"moderate": 2,
"minor": 1
},
"wcag_tag_coverage": {
"wcag2a": 4,
"wcag2aa": 5,
"wcag22aa": 1
},
"accessibility_score": 62,
"top_violations": [
{
"rule_id": "color-contrast",
"impact": "serious",
"description": "Ensures the contrast between foreground and background colors meets WCAG 2 AA contrast ratio thresholds",
"help": "Elements must meet minimum color contrast ratio thresholds",
"help_url": "https://dequeuniversity.com/rules/axe/4.10/color-contrast",
"wcag_tags": ["wcag2aa", "wcag143"],
"affected_nodes": 8,
"sample_selectors": [".nav-link", ".btn-secondary", "footer a"],
"sample_html": ["<a class='nav-link' ...", "<button class='btn-secondary' ...", "<a href='/privacy' ..."],
"failure_summary": "Fix any of the following:\n Element has insufficient color contrast of 3.2:1 ..."
}
]
}

๐Ÿ Python SDK Example

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("nexgendata/wcag-accessibility-auditor").call(run_input={
"urls": [
"https://example.com/",
"https://example.com/about"
]
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(f"{item['url']} โ†’ score {item['accessibility_score']} "
f"({item['total_violations']} violations)")
for v in item["top_violations"][:3]:
print(f" [{v['impact']}] {v['rule_id']} โ€” {v['affected_nodes']} nodes")

๐ŸŒ cURL Example

curl -X POST "https://api.apify.com/v2/acts/nexgendata~wcag-accessibility-auditor/run-sync-get-dataset-items?token=YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"urls": ["https://example.com/"]
}'

๐Ÿ”— Zapier / Make.com / GitHub Actions Integration

  • GitHub Action โ€” run on every PR, comment on violations introduced
  • Zapier โ€” new page published in CMS โ†’ audit โ†’ Slack alert if score drops
  • Weekly cron โ€” scan your whole sitemap, track score trends over time

โ“ FAQ

Q: What's the difference between this and Google Lighthouse's accessibility audit? Lighthouse also uses axe-core under the hood, but runs only on one page at a time from DevTools. This actor is a bulk API wrapper โ€” run it on 500 URLs programmatically and get machine-parseable JSON per page.

Q: What WCAG version is covered? WCAG 2.0, 2.1, and 2.2 (Level A and AA) by default. Configure the wcagTags input to narrow to a specific version.

Q: Does this catch all accessibility issues? No automated tool does. axe-core catches roughly 30-40% of WCAG issues โ€” primarily the objective ones (color contrast, missing alt text, missing labels, ARIA misuse). Human testing with screen readers is still needed for the full picture. But automated audits are the cheapest way to catch the bulk of fixable issues fast.

Q: Does it handle logged-in pages? Not yet. Pass only publicly-accessible URLs for now. Authentication support is on the roadmap.

Q: What's the accessibility score based on? Severity-weighted deduction: critical=-15, serious=-8, moderate=-3, minor=-1, scaled by affected node count. A clean site scores 100; typical SMB sites land in 50-80 range.

Q: Is axe-core's output reliable? Yes. axe-core is maintained by Deque Systems (the accessibility firm), is used by Microsoft, Google, IBM, Adobe, and has the lowest false-positive rate of any automated a11y scanner. It's the industry standard.

๐Ÿ’ฐ Pricing (Pay-Per-Event)

  • Actor start: $0.005
  • URL audited: $0.01

Typical run cost: 100-URL scan = $1.005. Compare with Siteimprove (~$10k/yr starter plans) or enterprise axe DevTools Pro ($495/user/yr).

๐Ÿš€ Apify Affiliate Program

New to Apify? Sign up with our referral link for free platform credits.


Automated WCAG 2.2 AA auditing for developers, agencies, and procurement teams who need real accessibility scans without enterprise SaaS pricing. Built by NexGenData.

๐Ÿ’ป Code Example โ€” Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("nexgendata/wcag-accessibility-auditor").call(run_input={
# Fill in the input shape from the actor's input_schema
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)

๐ŸŒ Code Example โ€” cURL

curl -X POST "https://api.apify.com/v2/acts/nexgendata~wcag-accessibility-auditor/run-sync-get-dataset-items?token=YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{ /* input schema */ }'

โ“ FAQ

Q: How do I get started? Sign up at apify.com, grab your API token from Settings โ†’ Integrations, and run the actor via the Apify console, API, Python SDK, or any integration (Zapier, Make.com, n8n).

Q: What's the typical cost per run? See the pricing section below. Most runs finish under $0.10 for typical batches.

Q: Is this actor maintained? Yes. NexGenData maintains 165+ Apify actors and ships updates regularly. Bug reports via the Apify console issues tab get responses within 24 hours.

Q: Can I use the output commercially? Yes โ€” you own the output data. Check the target site's Terms of Service for any usage restrictions on the scraped content itself.

Q: How do I handle rate limits? Apify manages concurrency and retries automatically. For very large batches (10K+ items), run multiple smaller jobs in parallel instead of one mega-job for better reliability.

๐Ÿ’ฐ Pricing

Pay-per-event pricing โ€” you only pay for what you actually extract.

  • Actor Start: $0.0001
  • result: $0.0050

๐Ÿš€ Apify Affiliate Program

New to Apify? Sign up with our referral link โ€” you get free platform credits on signup, and you help fund the maintenance of this actor fleet.

๐Ÿ“š More From NexGenData

Explore the full catalog, tutorials, Gumroad data packs, and newsletter at thenextgennexus.com โ€” the brand home for everything we ship.

  • ๐Ÿ“– Tutorials & how-to guides
  • ๐Ÿ—‚๏ธ Full actor catalog with usage examples
  • ๐Ÿ“ฆ Gumroad data packs (one-time purchases)
  • ๐Ÿ“ฌ Newsletter โ€” monthly drops of new actors and revenue experiments

Built and maintained by NexGenData โ€” 165+ actors covering scraping, enrichment, MCP servers, and automation. ๐Ÿ  Home: thenextgennexus.com