The shared 2.x foundation
- Perceivable, operable, understandable, and robust
- Level A and AA success criteria
- Full-page and complete-process conformance concepts
- Automated testing plus human evaluation
WCAG 2.2 AA accessibility testing API
Use WCAG 2.2 as a forward-looking technical target without pretending every success criterion can be automated. AccessPreflight reports machine findings, partial signals, and manual evaluation requirements as different outcomes.
Scanning profile
wcag-2.2-aa-webWCAG 2.2 AATechnical preflight
- Input
- Public URL or HTML
- Mapping
- WCAG 2.2 · Level A and AA
- Boundary
- Criteria-level coverage stays explicit
TargetLevel A + AA success criteria
Delta2.2 additions stay visible in the mapping
Human workMeaning, journeys, and user experience
Use WCAG 2.2 AA through the API.
Send wcag-2.2-aa-web with the asset and keep this profile’s evidence boundary in the returned result.
Keep the WCAG 2.2 delta visible.
A separate profile lets teams adopt the newer technical target while preserving WCAG 2.1 where a contract or legal mapping still requires it.
The 2.2 profile adds
- New focus appearance and obscuring criteria
- Dragging movement alternatives
- Target size minimum
- Consistent help
- Accessible authentication criteria
Make the 2.2 target an explicit project decision.
A pinned profile keeps the newer target visible in configuration instead of silently changing the meaning of historic results.
POST/v1/scansIllustrative- profile
- wcag-2.2-aa-web@1.2.0
- baseline
- release-candidate
- gate
- new_findings
The result records both requested and resolved profile versions.
Questions to resolve before the gate becomes policy.
A technical target is only useful when the team agrees how it enters releases and how manual work is owned.
Will existing findings block the first release?
Use a baseline if the first goal is to stop new regressions while the backlog is repaired.
Which new findings stop publication?
Define project thresholds without changing the underlying standard mapping.
Who owns criteria software cannot decide?
Keep the owner and checkpoint visible in the same result lifecycle.
Read the source behind this profile.
The WCAG 2.2 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.2 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.