# List WCAG failures on a website

**Use case:** 

Only the pages and documents that fail accessibility checks, with the issues found on each, as a remediation to-do list.

## Input

```json
{
  "startUrls": [
    "https://www.section508.gov/"
  ],
  "maxPages": 50,
  "maxPdfs": 25,
  "maxPdfSizeMb": 25,
  "checkHtmlPages": true,
  "onlyFailingItems": true,
  "maxConcurrency": 5
}
```

## Output

```json
{
  "type": {
    "label": "Type"
  },
  "url": {
    "label": "URL",
    "format": "string"
  },
  "passesBasicChecks": {
    "label": "Passes",
    "format": "boolean"
  },
  "criticalIssues": {
    "label": "Critical",
    "format": "number"
  },
  "tagged": {
    "label": "Tagged",
    "format": "boolean"
  },
  "hasText": {
    "label": "Has text",
    "format": "boolean"
  },
  "pages": {
    "label": "PDF pages",
    "format": "number"
  },
  "foundOn": {
    "label": "Linked from",
    "format": "link"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The ADA Title II Website & PDF Accessibility Auditor Actor is ready to run with the inputs already set for "List WCAG failures on a website". [Sign up or log in](https://console.apify.com/create-task-from-example/sUUL2Py5hfVKYYGhF) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "List WCAG failures on a website" task

The ADA Title II Website & PDF Accessibility Auditor Actor will start running based on the input automatically. You can also change all the input fields, like website(s) to audit, max web pages, and more, to match your specific use case.

### 3. Receive the "List WCAG failures on a website" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as type, URL, passes, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "List WCAG failures on a website" task via API](https://apify.com/dennydevelops/gov-accessibility-auditor.md).

## FAQ

### What does the accessibility audit check?

The ADA Title II Accessibility Auditor checks web pages and linked PDFs for common WCAG 2.1 AA problems such as missing alt text, untagged PDFs and missing titles.

### Why does ADA Title II matter?

The ADA Title II rule requires state and local government websites and documents to meet WCAG 2.1 AA, which is why public agencies audit their sites.

### Does it audit PDFs?

Yes. The ADA Title II Accessibility Auditor downloads linked PDFs and reports tagging, title, language and text-layer issues for each one.

## About this Actor

This example demonstrates how to use [ADA Title II Website & PDF Accessibility Auditor](https://apify.com/dennydevelops/gov-accessibility-auditor.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/dennydevelops/gov-accessibility-auditor.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/dennydevelops/gov-accessibility-auditor.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).