Accessibility Check API

WCAG accessibility check (static analysis): findings mapped to WCAG success criteria with A/AA/AAA levels — alt text, page title, lang, form labels, heading structure, table headers, link purpose, accessible names, duplicate IDs, ARIA role validity, zoom blocking, meta refresh, skip links. Filter with ?level=A|AA|AAA. Honestly reports what static analysis cannot check (contrast, focus, keyboard).

Parameters

Example request

curl "https://api.webbersites.com/api/a11y/check?url=https%3A%2F%2Fexample.com&level=AA"
# first call returns 402 + payment requirements; an x402 client pays and retries automatically

Example response

{
    "url": "https://example.com",
    "findings": [
        {
            "criterion": "1.1.1",
            "level": "A",
            "name": "Non-text content",
            "count": 6,
            "detail": "Images without usable text alternatives."
        }
    ],
    "totals": {
        "issues": 9,
        "by_level": {
            "A": 8,
            "AA": 1,
            "AAA": 0
        },
        "criteria_failed": 3
    },
    "not_checked": [
        "1.4.3 color contrast (needs rendering)"
    ]
}

How payment works

There is no signup and no API key. Call the endpoint; it replies 402 Payment Required with machine-readable payment requirements. Your client signs a USDC transfer authorization (EIP-3009, gasless) and retries with the X-PAYMENT header — @x402/fetch does this automatically. See the overview for a working snippet.