Accessibility Checker (axe-core) - WCAG Violations Audit avatar

Accessibility Checker (axe-core) - WCAG Violations Audit

Pricing

from $10.00 / 1,000 page auditeds

Go to Apify Store
Accessibility Checker (axe-core) - WCAG Violations Audit

Accessibility Checker (axe-core) - WCAG Violations Audit

Audits a public page with axe-core, the open-source accessibility engine used by Chrome DevTools, and returns every WCAG violation found (impact, affected elements, help URL). No login, no third-party API keys.

Pricing

from $10.00 / 1,000 page auditeds

Rating

0.0

(0)

Developer

Cuantic Data

Cuantic Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

Accessibility Checker (axe-core) — WCAG Violations Audit

Audits a public page with axe-core, the open-source accessibility engine used by Chrome DevTools, and returns every WCAG violation found, with its impact, affected elements and the official link to the fix. No third-party API keys, no login.

What it does

  • Loads the page with a real headless Chrome, injects axe-core, and runs its standard scan (the same rules used by the axe DevTools extension).
  • Returns violations sorted by impact (critical → serious → moderate → minor), each with help, helpUrl and up to 3 sample affected elements (nodeCount carries the real total).
  • Also returns how many rules passed (passesCount) and how many are incomplete (incompleteCount, cases that need manual review according to axe-core).

Who it's for

  • Teams that need an accessibility report before a launch or to meet a client/tender requirement.
  • Agencies auditing third-party sites in bulk.

Input

FieldTypeRequiredDescription
urlstringYesOne page per run (pay-per-event = 1 event per page).
waitForSelectorstringNoCSS selector to wait for before auditing, if content loads via JS and appears late.
{ "url": "https://example.com" }

Output

{
"url": "https://example.com",
"violations": [
{
"id": "landmark-one-main",
"impact": "moderate",
"description": "Ensure the document has a main landmark",
"help": "Document should have one main landmark",
"helpUrl": "https://dequeuniversity.com/rules/axe/4.13/landmark-one-main",
"tags": ["cat.semantics", "best-practice"],
"nodeCount": 1,
"sampleTargets": ["html"]
}
],
"violationCount": 2,
"passesCount": 13,
"incompleteCount": 0,
"inapplicableCount": 75,
"axeVersion": "4.13.0",
"checkedAt": "2026-09-20T03:34:11.819Z"
}

Pricing

Pay-per-event, provisional. Starting reference: USD 0.04 per page audited (03-plan.md §2).

How to call it

curl "https://api.apify.com/v2/acts/cuantic-data~accessibility-axe-checker/run-sync-get-dataset-items?token=YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"url": "https://example.com"}'

Terms and limits

See ./TERMS.md: uses axe-core (Mozilla Public License 2.0, commercial use allowed), running against the user's own page.

What it does NOT do

  • It doesn't fix anything automatically — it reports, with the official link to the fix.
  • If the page loads content via JavaScript after the network-idle event, that content may be left out of the audit unless you use waitForSelector.
  • It's not a legal certification of WCAG/ADA compliance: it's an automated technical audit that, by axe-core's own design, doesn't cover 100% of criteria (some require human review — those land in incompleteCount).

FAQ

Why does it say "incomplete" instead of pass or fail? axe-core flags cases it can't decide 100% automatically (e.g. whether an alt text is genuinely descriptive) — they need human review, it's not an Actor error.

Found a bug? Email cuanticwindows@gmail.com — we reply within 72 hours.


See build/README.md for how to run tests and publish this Actor.