WCAG Translator — developer language to WCAG guidance

Input

plain language

What is happening?

Version

Level

Matching runs on this server against the indexed W3C data.

Response

idle

Send a description, a checker rule id or a whole scan report. You get back the success criteria it maps to, why each one matched, and where the wording came from.

Context

POST /v1/translate

Run something on the left and the response that produced it appears here.

Every panel on this screen is rendered from this payload.

Endpoints

POST /v1/translateLanguage to criteria, with match basis and confidence.
POST /v1/translate/ruleChecker rule ids. Same result shape. Up to 100 per call.
POST /v1/reportA whole axe, Lighthouse or Pa11y report, rolled up by criterion.
GET /v1/coverageWhich criteria automation reaches, and which need a person.
GET /v1/search?q=Ranked search across criteria, techniques and glossary.
GET /v1/criteria/:idOne criterion, plus /coverage and /related.
GET /v1/techniques/:idOne technique, and the criteria it supports.
GET /v1/glossary/:termA WCAG glossary definition.
GET /v1/rulesEvery checker rule this build knows, filterable by criterion.
GET /v1/healthLiveness, plus the age of the indexed W3C data.

W3C allow reuse where their content stays intact and additions stay distinguishable, so provenance rides along in the response shape.

w3c: Principles, guidelines, success criteria, requirement HTML, glossary definitions and technique associations. Reproduced intact from the published W3C JSON.
axe-core: Checker rule ids, help text and the WCAG tags behind every rule mapping. Generated from axe-core at build time. MPL-2.0.
added here: The developer phrase dictionary, signal words, relevance scores, confidence labels, explanations and coverage analysis. Tagged source wherever it appears.