AccessDepth WCAG 2.1 AA Auditor

Accessibility audit per URL, in two layers:

1. Baseline (axe-core) — the well-known, reliable open-source ruleset (WCAG 2.1 A/AA tags).
2. Deep (real keyboard simulation) — a browser that actually tabs through the page: unreachable interactive elements, focus traps, and JS-only click handlers with no keyboard access. This is exactly the class of problem a static scanner cannot see, because it requires runtime behaviour rather than just reading the DOM.

Most accessibility scanners stop at the axe-core layer. The keyboard-navigation pass is what catches the issues real users with a keyboard or screen reader actually hit.

Input

{
  "startUrls": ["https://example.com", "https://example.com/contact"],
  "basicOnly": false
}

• startUrls — one or more page URLs. Each URL produces one item in the Dataset.
• basicOnly — skip the keyboard simulation for a faster, axe-core-only scan.

Output (per URL, one Dataset item)

{
  "url": "https://example.com",
  "httpStatus": 200,
  "pageTitle": "Example",
  "summary": { "totalIssues": 12, "critical": 1, "serious": 3, "moderate": 6, "minor": 2 },
  "basicViolations": [ /* axe-core violations, with WCAG criteria + concrete selectors */ ],
  "deepIssues": [ /* keyboard-navigation issues: unreachable, focus trap, no visible focus */ ]
}

Every issue points to the exact element on the page (CSS selector), so a developer can jump straight to the fix instead of guessing.

Politeness guarantees

• robots.txt is genuinely checked up front — a Disallow match skips that page.
• Exactly one navigation attempt per URL, no automatic retries.
• No forms submitted, no accounts created — purely reading and navigating.

Why it matters

The European Accessibility Act (EAA, in force since June 2025) and the rising wave of ADA lawsuits in the US make WCAG 2.1 AA compliance a real legal risk for online stores and SaaS products. This actor finds concrete, reproducible problems with the exact location on the page — not just a compliance percentage or a vague score.

Pricing

Pay-per-result: you are billed per URL audited, so a single-page spot check costs a fraction of a full-site crawl. Run it on demand, on a schedule, or wire it into your CI via the Apify API.