# US Government Title II ADA Accessibility Audit (`elab/us-gov-title-ii-ada-accessibility-audit`) Actor

WCAG 2.1 AA audit for US state/local government sites, with a Title II (28 CFR Part 35) legal report: deadline, all five scoping exceptions, and the affirmative defense. Real selectors, screenshots, executive summary. Automated scan, not legal advice. No charge on failures.

- **URL**: https://apify.com/elab/us-gov-title-ii-ada-accessibility-audit.md
- **Developed by:** [Barak Eliov](https://apify.com/elab) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $45.00 / 1,000 page auditeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

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 examples already wired to this Actor's own input schema, see the [API](#api) section below.

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`).

# README

## US Government Title II ADA Accessibility Audit

Audits US state/local government websites against **WCAG 2.1 AA** in a real Chromium browser, using the
[axe-core](https://github.com/dequelabs/axe-core) engine (MIT, Deque Systems), and produces a **Title II
legal-citation PDF report**: the DOJ's population-based compliance deadline, all five scoping exceptions
(28 CFR 35.201), and the non-strict-liability affirmative defense (28 CFR 35.204). Automated scan only,
not legal advice.

This is v1 (the scope approved in `SPEC.md`). See "What's not in v1 yet" below.

### What this Actor does

1. Audits every URL you supply at **WCAG 2.1 Level A and AA** - the exact minimum **28 CFR 35.200(b)(1)-(2)**
   requires for public entities covered by Title II of the Americans with Disabilities Act.
2. Produces a **Title II legal-citation PDF** with:
   - A one-page **executive summary** (readable in under 60 seconds by a city council member or
     procurement officer): the applicable compliance deadline, a compliance-posture percentage (pages
     with zero critical/serious findings), and the top risk items - framed explicitly as a summary of
     automated-scan results, never a certification.
   - The applicable **compliance deadline**, sourced to the DOJ's April 2026 Interim Final Rule (document
     2026-07663), with an explicit note that its comment period closed June 22, 2026 and it is not yet
     finalized.
   - All **five scoping exceptions** (28 CFR 35.201(a)-(e)) - archived content, preexisting conventional
     electronic documents, third-party-posted content, individualized password-protected documents, and
     preexisting social media posts.
   - The **affirmative defense** (28 CFR 35.204): a public entity may claim fundamental alteration or undue
     financial/administrative burden, with the burden of proof on the entity - stated without implying
     strict/absolute liability.
   - Every violation mapped to its WCAG success criterion, screenshots, and a batch rollup.
   - **Issues recurring across multiple sites in the same batch** - see "Cross-site recurring issues" below.
3. **Never charges for a failed or blocked audit.**

### What makes this different from the global WCAG-audit Actors on Apify

No other Apify Actor - including this Actor's own generic English sibling
(`elab/website-accessibility-wcag-audit-api`) and the one federal-only "government" adjacent Actor
(`malonestar/gsa-site-scanning-auditor`, which covers only ~29,600 federal `.gov` sites via a shallower,
non-axe-core engine) - cites the DOJ Title II legal text, its population-based deadlines, its five scoping
exceptions, or its affirmative defense. Confirmed by reading all three closest incumbents' live
READMEs/schemas (see `SPEC.md` section 2).

### Executive summary (read this first)

The legal PDF opens with a one-page executive summary - deliberately framed as a **summary of
automated-scan results**, never a pass/fail certification: the applicable deadline statement, a
compliance-posture percentage, the top risk items, and (for multi-site batches) the cross-site recurring
issues below. The full legal citation and per-page findings follow it.

### Cross-site recurring issues (for COGs and state municipal leagues)

When a batch covers **2 or more distinct hostnames** (e.g. a council of governments or a state municipal
league auditing many member-city sites in one run), the summary row's `recurringAcrossSites` field and the
legal report's executive summary both list axe-core rules confirmed as violations on multiple sites -
useful because many municipal sites share the same vendor CMS/template, so one fix often applies to every
affected site. This is a mechanical count of recurring rule IDs across hostnames, computed from already-
confirmed violations - **not** a legal determination and **not** a per-finding scoping-exception
classification (see "What this Actor will never auto-decide" below). Empty for single-site batches.

### What this Actor will never auto-decide

Whether any of the five scoping exceptions (28 CFR 35.201) or the affirmative defense (28 CFR 35.204)
applies to a specific page or document requires human legal judgment. This Actor **never** attempts to
auto-classify a finding against a scoping exception or the affirmative defense - those are stated as
general legal content in the report, not as a per-row flag. Consult a lawyer and/or a certified
accessibility auditor before relying on this report for compliance purposes.

### Important legal disclaimer (read before relying on the report)

**This report is an automated scan (axe-core on a real browser). It is not a certified legal audit, not a
legal opinion, not an official conformance certificate, and not a DOJ determination of Title II
compliance.** It does not guarantee any legal outcome or full compliance with 28 CFR Part 35 Subpart H.

### Standing legal-monitoring note

The April 26, 2027 / April 26, 2028 compliance dates are correct **only** as amended by the DOJ's April
2026 Interim Final Rule (document 2026-07663). That rule's public comment period closed June 22, 2026 and
it **is not yet finalized** - if DOJ issues a final rule that changes any date or exception, this Actor's
legal content (`src/legalContentUs.ts`) must be updated before the next report is trusted. The original
2024 final rule's earlier dates no longer apply and never appear anywhere in this Actor's output.

### Input example

```json
{
  "urls": ["https://www.example-city.gov"],
  "wcagLevel": "wcag21aa",
  "entityPopulationTier": "50000_or_more",
  "entityName": "City of Example",
  "generateLegalReport": true
}
```

### Input defaults

Every input field has a default. `.actor/input_schema.json` is the authoritative source; this table is
generated from it and the defaults below match that file exactly.

| Field | Type | Default | Meaning |
| --- | --- | --- | --- |
| `urls` | array | `["https://www.usa.gov"]` | Public page URLs to audit, one audit per URL (up to 100 per run). No crawling. |
| `wcagLevel` | string | `"wcag21aa"` | WCAG level to check. `wcag21aa` is the minimum 28 CFR 35.200(b)(1)-(2) requires. |
| `entityPopulationTier` | string | `"unknown"` | Population tier of the audited entity, used only to state the correct deadline. Never inferred from a URL. |
| `entityName` | string | `""` | Optional, purely cosmetic entity name for the legal report's cover page. |
| `viewport` | string | `"desktop"` | Screen preset: `desktop`, `tablet`, `mobile`, or `custom`. |
| `viewportWidth` | integer | `1280` | Custom viewport width in px (used only when `viewport` is `custom`). |
| `viewportHeight` | integer | `800` | Custom viewport height in px (used only when `viewport` is `custom`). |
| `includeScreenshots` | boolean | `true` | Element screenshot per violation plus one full-page screenshot per URL. |
| `includeIncomplete` | boolean | `true` | Also return axe-core checks that need human review (`status` = `incomplete`). |
| `includePasses` | boolean | `false` | Also return the count of rules that passed. |
| `outputMode` | string | `"both"` | Row shapes: `perPage`, `flat`, or `both`. One `page-audited` charge per successful page in every mode. |
| `generateLegalReport` | boolean | `true` | Generate the Title II legal-citation PDF report for the run (charged only on success). |
| `generatePdfReport` | boolean | `false` | Also generate a plain WCAG-only PDF report, no legal citation (charged only on success). |
| `waitForSelector` | string | `""` | Optional CSS selector to wait for before auditing. Empty means no wait. |
| `waitUntil` | string | `"load"` | Navigation readiness: `load`, `domcontentloaded`, or `networkidle`. |
| `timeoutSecs` | integer | `30` | Per-URL time budget in seconds for navigation, audit and screenshots. |
| `proxyConfiguration` | object | `{"useApifyProxy":true}` | Apify Proxy settings used for the audit requests. |
| `maxConcurrency` | integer | `5` | Maximum number of pages audited in parallel within one run. |

### Output example

The dataset has three row shapes, distinguished by `rowType`.

**Page row** (one per audited URL):

```json
{
  "rowType": "page",
  "url": "https://www.example-city.gov",
  "finalUrl": "https://www.example-city.gov/",
  "status": "success",
  "wcagLevel": "wcag21aa",
  "viewport": "desktop",
  "score": 88,
  "violationCount": 2,
  "incompleteCount": 0,
  "passCount": 0,
  "violationsByImpact": { "critical": 0, "serious": 0, "moderate": 2, "minor": 0 },
  "fullPageScreenshotUrl": "https://api.apify.com/v2/key-value-stores/.../records/fullpage-....png",
  "waitForSelectorTimedOut": false,
  "errorCategory": null,
  "errorMessage": null,
  "auditedAt": "2026-10-07T12:00:00.000Z",
  "engineVersion": "4.13.0"
}
```

**Violation row** (one per individual finding, when `outputMode` is `flat`/`both`):

```json
{
  "rowType": "violation",
  "pageUrl": "https://www.example-city.gov",
  "ruleId": "image-alt",
  "impact": "critical",
  "status": "violation",
  "description": "Images must have alternate text",
  "helpText": "Add an alt attribute",
  "helpUrl": "https://dequeuniversity.com/rules/axe/4.13/image-alt",
  "wcagCriteria": ["1.1.1"],
  "selector": "#logo",
  "htmlSnippet": "<img id=\"logo\">",
  "screenshotUrl": "https://api.apify.com/v2/key-value-stores/.../records/violation-....png",
  "nodeCount": 1
}
```

**Summary row** (exactly one per run, also saved to the key-value store as `batchSummary`):

```json
{
  "rowType": "summary",
  "totalPagesAudited": 1,
  "totalPagesFailed": 0,
  "totalViolations": 1,
  "violationsByImpact": { "critical": 1, "serious": 0, "moderate": 0, "minor": 0 },
  "topFailingRules": [{ "ruleId": "image-alt", "pageCount": 1 }],
  "pdfReportUrl": null,
  "legalReportUrl": "https://api.apify.com/v2/key-value-stores/.../records/legal-report-....pdf",
  "applicableDeadline": null,
  "titleIICitation": {
    "regulation": "28 CFR Part 35 Subpart H (ADA Title II)",
    "standard": "WCAG 2.1 Level A and AA (28 CFR 35.200(b)(1)-(2))",
    "deadlineSource": "Current compliance dates per the DOJ's April 2026 Interim Final Rule (document 2026-07663); original 2024 final rule dates differ and no longer apply. IFR comment period closed June 22, 2026 - re-verify once DOJ issues a final rule.",
    "scopingExceptions": "28 CFR 35.201(a)-(e): archived web content; preexisting conventional electronic documents not needed for current services; third-party-posted content without a contractual/licensing arrangement; individualized password-protected documents about a specific individual; preexisting social media posts.",
    "affirmativeDefense": "28 CFR 35.204: a public entity may claim fundamental alteration or undue financial/administrative burden as a defense, with the burden of proof on the entity and a written-determination requirement. Compliance is not absolute or strict - this defense exists.",
    "sources": ["https://www.govinfo.gov/ (28 CFR 35.200-35.204)", "https://public-inspection.federalregister.gov/2026-07663.pdf"],
    "disclaimer": "This report is an automated scan, not a legal opinion or an official conformance certificate."
  },
  "recurringAcrossSites": []
}
```

`applicableDeadline` is `null` above because `entityPopulationTier` was left at its default, `"unknown"` -
the legal report then states **both** deadlines with an explicit prompt to confirm classification, never
silently defaulting to one. Set `entityPopulationTier` to get a single dated `applicableDeadline`.

`recurringAcrossSites` is populated only when the batch covers 2+ distinct hostnames and a rule recurs on
2 or more of them - see "Cross-site recurring issues" above.

### Errors (never silent, never charged)

| Category | When |
|---|---|
| `invalid_url` | Malformed URL, non-http(s) URL, or the URL resolves to a private/link-local/reserved IP address (SSRF protection, always on) |
| `not_found` | DNS failure, connection refused, 404/410 |
| `blocked` | 401/403/429 response, or a Chromium block error (e.g. `ERR_BLOCKED_BY_RESPONSE`) - common on state/local government CDN/WAF setups (Akamai/Incapsula). Never retried |
| `timeout` | Navigation, the axe-core audit, or screenshot capture exceeded `timeoutSecs` combined |
| `render_error` | Browser crash or an unclassified render failure |
| `upstream_changed` | 5xx upstream server error |

A failed page is **never charged**. A legal report that cannot be produced (zero pages succeeded in the
batch) is **not charged** either - `page-audited` charges for pages that did succeed in the same batch are
unaffected.

### Report size limits (dataset vs. PDF)

With `outputMode` `flat` or `both`, the **dataset** is complete: every violation/incomplete finding for every
URL is a full row, regardless of batch size. The limits below apply only to what's embedded in full detail
(HTML snippet + screenshot image) inside the **PDF report body** (`generatePdfReport` and/or
`generateLegalReport`):

- **Per page**: at most 20 findings embedded in full, confirmed violations before "needs manual review"
  items, most severe first.
- **Per batch**: a shared ceiling of 200 findings embedded in full across the whole run (up to the
  100-URL-per-run maximum).
- Whatever is held back is **never silently dropped** - the report prints exactly how many additional
  findings exist on that page and how many of them are confirmed violations vs. items needing manual
  review, with a pointer to the full dataset.
- PDF rendering has an internal **3-minute outer deadline** for the whole batch. If exceeded, generation
  is aborted, logged, and **not charged** - page-level `page-audited` charges already applied in the same
  run are unaffected.

This cap is ported unchanged from the already-live generic sibling (`src/reportCaps.ts`), where it fixed a
real unbounded-PDF-cost bug (`docs/lessons.md` #1) - never reintroduced or re-broken here.

### Pay-per-event pricing

| Event key | When |
|---|---|
| `page-audited` | One page successfully audited, including screenshots |
| `legal-report-generated` | The Title II legal-citation report was produced successfully (default: on) |
| `report-generated` | The plain WCAG-only PDF report was produced successfully (default: off) |

Every event name is checked against Apify Console's event-key charset (`^[a-zA-Z0-9_-]{1,256}$`, no
spaces) in `tests/events.test.ts` before a build is considered done.

### Local development / Apify run

```bash
npm install
npx playwright install chromium   # one-time
npm run typecheck
npm test
npm run build
apify run --input-file smoke-input.json --purge
```

### Use with AI agents / MCP

Call with `urls` as an array (never comma-separated). Check `rowType` first, then `status`/`errorCategory`
on page rows. `summary.legalReportUrl`, `summary.applicableDeadline`, `summary.titleIICitation`, and
`summary.recurringAcrossSites` are this Actor's government-specific fields on top of the generic WCAG
sibling's schema - everything else is identical.

### FAQ

**Am I charged for a failed or blocked audit?** No. This is this Actor's central guarantee.

**Is the legal report legal advice?** No. See "Important legal disclaimer" above.

**Will this tell me which scoping exception applies to my site?** No - by design. See "What this Actor
will never auto-decide" above.

**Are the April 26, 2027 / 2028 dates final?** No - they come from a DOJ Interim Final Rule whose comment
period closed June 22, 2026 and which is not yet finalized. See "Standing legal-monitoring note" above.

### What's not in v1 yet

- **Per-entity grouped batch reports.** This v1 produces one legal report per run, covering every URL in
  that run (with `entityName`/`entityPopulationTier` applied uniformly to the whole batch) - it does not
  yet accept a per-URL entity mapping to split one run's URLs into separate per-entity report sections.
  For now, a COG/municipal league auditing multiple distinct entities with different names or population
  tiers should run this Actor once per entity (the cross-site recurring-issues feature above still works
  within a single run across that entity's own sites). A true multi-entity, per-entity-grouped report is
  a real, identified v1.1 candidate - intentionally not built in this pass to avoid half-building a new
  input shape beyond the approved spec.
- Site-crawl/auto-discovery, CI/CD webhooks, scheduled audits, custom rule-set authoring - the same
  explicit deferral list as the generic sibling.

# Actor input Schema

## `urls` (type: `array`):

Public page URLs to audit. Each URL produces one audit. This tool only checks the pages you provide - it does not crawl or discover other pages itself. Up to 100 URLs per run (useful for a COG or state municipal league auditing many member-city sites in one batch - see 'Issues recurring across multiple sites').

## `wcagLevel` (type: `string`):

WCAG level/version to check against. 'wcag21aa' (default) is the exact minimum 28 CFR 35.200(b)(1)-(2) requires for covered public entities. wcag22aa is an extended superset that also meets this minimum and additionally covers newer criteria relevant to mobile.

## `entityPopulationTier` (type: `string`):

Population tier of the public entity that owns the audited site(s) - used only to state the correct Title II compliance deadline in the legal report (see dropdown options for exact dates, current per the DOJ's April 2026 Interim Final Rule, doc 2026-07663, amending 28 CFR 35.200). Leave 'unknown' (default) to have the report state both deadlines with a prompt to confirm classification - this Actor never infers population from a URL.

## `entityName` (type: `string`):

Optional name of the public entity (e.g. 'City of Example') to print on the legal report's executive-summary cover page. Purely cosmetic - never used to look up or infer anything about the entity.

## `viewport` (type: `string`):

Screen resolution used for the audit. 'mobile' catches mobile-relevant violations (e.g. the WCAG 2.2 Target Size rule) that a desktop-only check would miss.

## `viewportWidth` (type: `integer`):

Used only when Viewport is set to 'custom'.

## `viewportHeight` (type: `integer`):

Used only when Viewport is set to 'custom'.

## `includeScreenshots` (type: `boolean`):

A focused screenshot for each violation, plus a full-page screenshot for each URL. Included in the 'page-audited' event price - no extra charge.

## `includeIncomplete` (type: `boolean`):

Also include axe-core 'incomplete' checks that need human review, alongside confirmed violations. The 'status' field in each row distinguishes 'violation' (confirmed) from 'incomplete' (needs review) - they are never merged.

## `includePasses` (type: `boolean`):

Also return the count of rules that passed. Off by default to keep output focused on actionable findings.

## `outputMode` (type: `string`):

'perPage' returns one page row per URL with a violationsByImpact summary. 'flat' returns one page row per URL plus one violation row per individual finding (suited to spreadsheets and ticketing systems). 'both' returns the same rows as 'flat', tagged by the 'rowType' field. Failed URLs get an error page row in every mode, never charged.

## `generateLegalReport` (type: `boolean`):

Generate one Title II legal-citation PDF per run: executive summary, compliance deadline, the WCAG 2.1 AA requirement (28 CFR 35.200), all five scoping exceptions (28 CFR 35.201), the undue-burden affirmative defense (28 CFR 35.204), violations mapped to WCAG criteria, screenshots, and a batch rollup incl. issues recurring across sites. Core differentiator, on by default. Automated scan only, not legal advice (see README). Charged as 'legal-report-generated', only on success.

## `generatePdfReport` (type: `boolean`):

Generate an additional plain PDF report without the Title II legal context, for buyers who want a pure WCAG report. Charged separately as 'report-generated', only when generation succeeds. Off by default; the Title II legal report above is the recommended report for this Actor's target audience.

## `waitForSelector` (type: `string`):

Optional CSS selector to wait for before auditing (for SPAs and client-rendered content). If the selector does not appear within the time budget, the page is still audited and 'waitForSelectorTimedOut' is set to true instead of failing.

## `waitUntil` (type: `string`):

When to start the audit. 'load' (default, recommended) is reliable even on complex government sites with continuous ad/analytics/agenda-widget network activity. 'networkidle' waits for the network to go quiet - more thorough for slow-loading content, but often never happens on many real sites and causes timeouts. 'domcontentloaded' is fastest but may run before late-loading content appears.

## `timeoutSecs` (type: `integer`):

Maximum seconds for navigation, axe-core checks and screenshot combined, before a URL is marked as a timeout error (not charged).

## `proxyConfiguration` (type: `object`):

Apify Proxy settings for the audit request.

## `maxConcurrency` (type: `integer`):

Maximum number of pages audited in parallel within a single run.

## Actor input object example

```json
{
  "urls": [
    "https://www.usa.gov"
  ],
  "wcagLevel": "wcag21aa",
  "entityPopulationTier": "unknown",
  "entityName": "",
  "viewport": "desktop",
  "viewportWidth": 1280,
  "viewportHeight": 800,
  "includeScreenshots": true,
  "includeIncomplete": true,
  "includePasses": false,
  "outputMode": "both",
  "generateLegalReport": true,
  "generatePdfReport": false,
  "waitForSelector": "",
  "waitUntil": "load",
  "timeoutSecs": 30,
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

One row per audited URL (rowType "page"), optionally one row per individual finding (rowType "violation", when outputMode is "flat"/"both"), and exactly one batch rollup row (rowType "summary", including applicableDeadline, titleIICitation, and recurringAcrossSites).

## `files` (type: `string`):

Full-page and element-cropped PNG screenshots referenced by fullPageScreenshotUrl/screenshotUrl in dataset rows; the 'batchSummary' record; the Title II legal-citation PDF (when generateLegalReport is true, the default) referenced by summary.legalReportUrl; and the optional plain WCAG-only PDF (when generatePdfReport is true) referenced by summary.pdfReportUrl.

# 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 = {
    "urls": [
        "https://www.usa.gov"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("elab/us-gov-title-ii-ada-accessibility-audit").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 = {
    "urls": ["https://www.usa.gov"],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("elab/us-gov-title-ii-ada-accessibility-audit").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 '{
  "urls": [
    "https://www.usa.gov"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call elab/us-gov-title-ii-ada-accessibility-audit --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,elab/us-gov-title-ii-ada-accessibility-audit"
        }
    }
}
```

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/3NwQ6m2Wk9G0Qdj8C/builds/mTKOVEdOo1zmK4DoT/openapi.json