WCAG 2.2 AA accessibility API

Adopt WCAG 2.2 as an explicit technical target without silently changing older results. Every scan resolves the requested profile version and separates observable browser conditions from complete user-journey review.

For product teams moving their technical baseline to WCAG 2.2

API profilewcag-2.2-aa-web@1.2.0

Check a website free Book a demo

Illustrative request202 Accepted

POST /v1/scans
Idempotency-Key: a82b91…

{
  "asset": {
    "type": "url",
    "url": "https://shop.example/checkout"
  },
  "profiles": [
    "wcag-2.2-aa-web@1.2.0"
  ],
  "metadata": {
    "commit_sha": "a82b91…"
  }
}

queuedid: scn_01J…profile resolved

Target: WCAG 2.2 Level A + AA
Lifecycle: 202 Accepted → signed completion
Boundary: 2.2 criteria coverage remains explicit

Move to 2.2 without rewriting history.

Profile pinning lets one project keep a contractual 2.1 baseline while another release path adopts the newer technical target.

The API pins

Requested and resolved profile versions
Rule and browser engine versions
Finding fingerprints for later comparison
Coverage decisions for each tested condition

Your team controls

When the 2.2 profile enters a release gate
Which severities block a build
Which baseline represents accepted debt
How manual evaluation enters the workflow

Read the WCAG 2.2 response as coverage, evidence, and open work.

A passing rule does not settle a complete criterion. The API keeps each supported condition inside the wider evaluation boundary.

Technical centerwcag-2.2-aa-web@1.2.0

Machine

Deterministic

Observed browser conditions

Partial

Supporting signal

Useful but not complete

Manual

Human evaluation

Meaning and complete journeys

Evidence

Reproducible

Locator, state, and profile

Treat the newer criteria as testable work, not a single score.

The profile can narrow the review surface, but interaction quality and complete processes still need deliberate evaluation.

Observable

Rendered conditions

Record machine-verifiable failures and the browser state that produced them.

Contextual

Partial signals

Flag conditions that reduce review work without deciding the entire criterion.

Experiential

Human journeys

Queue focus usability, authentication, help, and complete-task evaluation for people.

Inspect the policy behind the API profile.

Before WCAG 2.2 AA becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.

Read the WCAG 2.2 AA profile W3C Recommendation: WCAG 2.2

Put the WCAG 2.2 AA API in the path you already own.

Start with one asset flow, pin the profile, and keep evidence and unresolved human work attached to every result.

Check a website free Create an account

Automated preflight is not an accessibility certification or legal determination.