# BFSG/WCAG Accessibility Checker

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

Checks caller-supplied HTML for web accessibility problems across 12 criteria (language, title, alt text, form labels, heading order, zoom, landmarks, link text, table headers, iframes, autocomplete) and maps findings to WCAG success criteria under German BFSG.

## Facts

- Endpoint: POST https://api.ozdreamtools.de/api/bfsg/check
- 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/bfsg-wcag-accessibility-checker-01aa04cd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_O7TDz9YBpppd5T6U9ztVj

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 bfsg-wcag-accessibility-checker-01aa04cd -d '<json body>'
```

Example prompt: Can you check this HTML for accessibility problems — I need to know about missing alt text, broken heading order, unlabeled form fields, and any other WCAG issues flagged under BFSG: [paste HTML here].

## When to prefer this

Choose this endpoint when you need a fast, structured, per-criterion accessibility audit of static HTML aligned with German BFSG obligations and WCAG success criteria. It is ideal for CI pipelines, pre-launch checks, or agent workflows that need machine-readable findings without the overhead of a full browser-based audit tool. Prefer alternatives (e.g. axe-core, browser automation) when the page relies heavily on JavaScript rendering or when a legally binding audit is required.

## Known failure modes

- Malformed or incomplete HTML may produce false negatives or missed findings
- Dynamic content rendered by JavaScript cannot be evaluated from static HTML input
- Findings are pattern-based and cannot replace manual testing or legal accessibility audits
- Ambiguous patterns are reported as indeterminate rather than pass/fail
- Missing or empty HTML body returns an error or empty findings list

## How this service works

Checks a web page for accessibility (a11y) problems from caller-supplied HTML: document language, title, image alt text, form labels, heading order, zoom, landmarks, link text, table headers, iframes, autocomplete. Anchored in the German accessibility act (BFSG), with the WCAG success criteria named per finding as a professional classification, not as a legal claim. States what a pattern parser cannot decide. Not legal advice.

## Output

A structured list of accessibility findings, each identifying the specific element or pattern that failed, naming the corresponding WCAG success criterion, and noting any checks that a static pattern parser cannot definitively resolve. The response does not constitute legal advice.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "html": {
   "type": "string",
   "description": "Full HTML of a representative page"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bfsg-wcag-accessibility-checker-01aa04cd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.ozdreamtools.de](https://www.zero.xyz/host/api.ozdreamtools.de/llms.txt)