# Batch WCAG 2.2 Accessibility Checker

> Batch WCAG 2.2 Accessibility Checker is a paid API for AI agents from api.agentstools.dev, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Runs static WCAG 2.2 accessibility checks on multiple UI markup files at once, returning per-file verdicts (pass/caution/block) and a rollup summary.

## Facts

- Endpoint: POST https://api.agentstools.dev/a11y/batch
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/batch-wcag-2-2-accessibility-checker-0c2ffac1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gK1lzlAjKYXYuwZyyhjrB

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability batch-wcag-2-2-accessibility-checker-0c2ffac1 -d '<json body>'
```

Example prompt: Can you run a WCAG 2.2 AA accessibility audit on these five JSX component files I'm uploading — give me a pass/caution/block verdict for each one and a rollup of the worst issues across all of them?

## When to prefer this

Choose this endpoint when you need to audit multiple UI files in a single API call rather than checking them one at a time. It is ideal for CI/CD pipelines, design system releases, or bulk triage of a codebase where you want a consistent per-file verdict plus an aggregate rollup. Prefer it over single-file checkers when batch throughput and a unified worst-verdict rollup are important.

## Known failure modes

- Missing required 'files' array results in a 400 validation error
- Empty files array may return an empty results list with no rollup
- Unsupported framework value outside the enum causes a validation error
- Malformed or non-parseable markup may yield incomplete analysis for that file
- Invalid WCAG level value outside A/AA causes a schema validation failure
- Network timeout for very large batches may result in a 5xx error

## How this service works

Batch static accessibility (WCAG 2.2) check of many UI files at once: a list of objects each with a filename, optional framework and markup. Returns a per-file pass, caution or block verdict plus a rollup with the worst verdict and totals by severity. Accessibility indicators, not a legal compliance guarantee.

## Output

Returns a list of per-file results each containing the filename and a verdict of pass, caution, or block based on detected accessibility issues, plus a rollup object with the single worst verdict across all files and totals broken down by severity level. These are static analysis indicators, not a legal compliance guarantee.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "files": {
   "type": "array",
   "items": {
    "type": "object"
   },
   "description": "List of objects, each with filename, optional framework and markup"
  },
  "level": {
   "enum": [
    "A",
    "AA"
   ],
   "type": "string",
   "description": "Default WCAG level for every file (default AA)"
  },
  "framework": {
   "enum": [
    "auto",
    "html",
    "jsx",
    "tsx",
    "vue",
    "angular"
   ],
   "type": "string",
   "description": "Default framework for files that do not set one"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/batch-wcag-2-2-accessibility-checker-0c2ffac1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.agentstools.dev](https://www.zero.xyz/host/api.agentstools.dev/llms.txt)