$2 per result

Accessibility Audit

Check WCAG accessibility issues using axe-core in a real browser.

Run it on Apify All tools

Who it is for

Teams with a WCAG obligation, and anyone who wants the automated failures found before a user finds them.

What you would use it for

• Run axe-core against a page in a real browser and get every violation as JSON.
• Check a site before an accessibility statement or procurement review.
• Track violation counts across a set of pages over time.
• Feed failures straight into an issue tracker instead of transcribing a PDF.

What you get back

One JSON record per page checked. These are the actual fields returned by the most recent successful run — read from the live catalogue, not a documented ideal.

Sample output

Trimmed from a real run.

{
  "actor": "artifact-machine-accessibility-audit",
  "actorVersion": "0.1.0",
  "auditedAt": "2026-07-29T05:04:04.671Z",
  "url": "https://neighbornest.kids/",
  "finalUrl": "https://neighbornest.kids/",
  "origin": "https://neighbornest.kids",
  "score": 85,
  "grade": "B",
  "issueCounts": {
    "critical": 0,
    "high": 2,
    "medium": 1,
    "low": 0,
    "total": 3
  },
  "checks": {
    "pageStatus": 200,
    "pageTitle": "NeighborNest — Local care, camps, clubs & family services",
    "violationCount": 2,
    "passCount": 40,
    "incompleteCount": 1,
    "inapplicableCount": 50,
    "tags": [
      "wcag2a",
      "wcag2aa",

Pricing

$2 per result. Pay-per-event through Apify — no subscription, and a run that returns nothing costs nothing.

Calling it from code

Any HTTP client works. Replace <TOKEN> with your Apify API token.

curl -X POST "https://api.apify.com/v2/acts/artifact-machine~artifact-machine-accessibility-audit/run-sync-get-dataset-items?token=<TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"startUrls":[{"url":"https://example.com"}]}'

Questions

Does passing this mean the site is accessible?

No, and no automated tool can tell you that. Automated testing reliably catches roughly a third of WCAG issues — things like contrast, labels and ARIA misuse. Keyboard traps, focus order and whether alt text is meaningful still need a human. This finds the machine-checkable failures fast so the human review can start further along.

Which ruleset does it use?

axe-core, run in a real browser so that JavaScript-rendered content is evaluated as a user would receive it.

Other tools

Schema Audit - JSON-LD Structured Data Validator · Security Headers Checker · Sitemap Health Audit - XML Sitemap Validator · Tech Stack Analyzer - Detect Website Technologies

Details read from the live Apify catalogue on 2026-07-29.