# AccessDepth WCAG 2.1 AA Auditor (`vast_walnut_qrq/accessdepth-wcag-auditor`) Actor

Accessibility audit per URL: axe-core baseline plus a real keyboard-navigation simulation (tab order, focus traps, keyboard-only reachability) that static scanners miss. For WCAG 2.1 AA, EAA and ADA compliance.

- **URL**: https://apify.com/vast\_walnut\_qrq/accessdepth-wcag-auditor.md
- **Developed by:** [Abdellah Ouadoudi](https://apify.com/vast_walnut_qrq) (community)
- **Categories:** Developer tools, SEO tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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

```json
{
  "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)

```json
{
  "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.

# Actor input Schema

## `startUrls` (type: `array`):

One or more page URLs. Each URL produces one result in the Dataset (pay-per-result).

## `basicOnly` (type: `boolean`):

Skip the keyboard-navigation simulation and run only the fast axe-core layer.

## Actor input object example

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

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        "https://example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("vast_walnut_qrq/accessdepth-wcag-auditor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "startUrls": ["https://example.com"] }

# Run the Actor and wait for it to finish
run = client.actor("vast_walnut_qrq/accessdepth-wcag-auditor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    "https://example.com"
  ]
}' |
apify call vast_walnut_qrq/accessdepth-wcag-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,vast_walnut_qrq/accessdepth-wcag-auditor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/nW9TIfXP5q9McbxTo/builds/9ov0S56Oi0d3fOxqf/openapi.json
