WCAG 2.1 AA accessibility testing API

Test rendered pages or supplied HTML against selected machine-verifiable conditions mapped to WCAG 2.1 Level A and AA. Keep criterion coverage, rule evidence, and the work that still needs human evaluation in the same result.

Scanning profilewcag-2.1-aa-web
WCAG 2.1 AATechnical preflight
Input
Public URL or HTML
Mapping
WCAG 2.1 · Level A and AA
Boundary
Automated, partial, and manual coverage
PrinciplesPerceivable · Operable · Understandable · Robust
ResultFinding + criterion + evidence + coverage
GateAll findings or new findings only

Use WCAG 2.1 AA through the API.

Send wcag-2.1-aa-web with the asset and keep this profile’s evidence boundary in the returned result.

Explore the WCAG 2.1 AA API

Four principles enter one inspectable release record.

The profile keeps WCAG's organizing principles visible without compressing them into a single score or implying equal automated coverage.

P

Perceivable

Alternatives, structure, presentation

O

Operable

Keyboard, focus, navigation

U

Understandable

Language, labels, recovery

R

Robust

Names, roles, values, status

Use the profile as a repeatable release gate.

Pin the profile, compare with a baseline, and route the result without rewriting the integration when the source page changes.

  1. 1

    Scan the rendered state

    Submit a public URL or supplied HTML in the target environment.

  2. 2

    Classify the delta

    Separate new, recurring, resolved, and suppressed findings.

  3. 3

    Route unresolved work

    Fail the gate, create a repair task, and preserve manual checkpoints.

A WCAG finding should survive the handoff.

The evidence record ties a failed condition to the page state and the exact profile that produced it.

Illustrative resultreview_required
Profile
wcag-2.1-aa-web · resolved version
Criterion
WCAG success-criterion reference
Location
URL + selector + rendered evidence
Coverage
Automated / partial / manual

Read the source behind this profile.

The WCAG 2.1 AA source and its legal or standards context can change. AccessPreflight pins the profile version used for a scan; your organization should re-review applicability and the source when requirements change.

Run WCAG 2.1 AA where content enters the workflow.

Keep the profile, coverage boundary, evidence, and human-review queue attached to every result.

Check a website freeCreate an account

Automated preflight is not an accessibility certification or legal determination.