WCAG 2.2 Level AA · 56 Success Criteria

Scan. Evaluate. Document. Prove.
Your WCAG 2.2 Accessibility Evidence Journey

Accessibility compliance is no longer just about fixing violations. Procurement now requires documented governance: a VPAT, a named owner, a current accessibility statement, and evidence that issues are tracked and fixed. SysWisdom generates that evidence package automatically.

axe-core + Playwright Technical + Governance split Human sign-off required

01 Your WCAG 2.2 Evidence Journey

8 Steps to Evidence Readiness

Each step produces structured, auditable evidence. Technical violations and governance gaps remain separate throughout, never collapsed into a single score.

02 Define Your Assessment

Step 1 of 4

Choose Scope

URL & Evidence

Review Scope

Run Assessment

Why now

ADA Title II requires state and local government websites and apps, including AI chat widgets, to meet WCAG 2.1 AA. Larger jurisdictions had until April 24, 2026. Smaller entities, including most community colleges and special districts, must comply by April 26, 2027. ADA.gov guidance

For federal contracts and procurement, Section 508 requires an ACR (Accessibility Conformance Report). This assessment's evidence package supports that documentation.

What type of digital product are you assessing for WCAG 2.2 AA conformance?

✅

WCAG 2.2 AA: No Critical Violations

Evidence Score

WCAG 2.2 LEVEL AA: ACCESSIBILITY EVIDENCE READINESS REPORT

URL: -

Standard: WCAG 2.2 Level AA

Scope: -

Engine: axe-core · Playwright

Scan ID: -

Generated: -

Section 1: Automated Scan Summary

Section 2A: Technical Violations

Directly testable WCAG 2.2 failures found by axe-core. Grouped by impact, most severe first. These are engineering defects, not documentation issues.

Section 2B: Governance Documentation Gaps

Documentation and ownership deficiencies, separate from technical violations above. Both must be addressed. A clean automated scan with no governance documentation does not constitute a conformance claim.

Section 3: Evidence Quality Scorecard

These four axes are intentionally NOT collapsed into a single score. Low Traceability with high Completeness indicates a different risk than low Completeness with high Traceability. Procurement reviewers and governance owners should read each axis independently.

Section 4: Remediation Recommendations

SysWisdom is vendor-neutral. Tools listed are illustrative examples of each remediation category, not endorsements.

Section 5: Evidence Inventory

Section 6: Human Oversight & Audit Trail

Evidence Package Ready

WCAG violations · governance gaps · C/C/V/T scorecard · recommendations

03 Human Oversight Model

WCAG conformance is a human accountability decision, not an automated verdict. SysWisdom surfaces violations and evidence gaps: a named person must own the governance sign-off.

🟢

No Critical / Serious Violations

Automated scan passes major criteria. Governance documentation review required before claiming conformance.

Governance review

🟡

Moderate / Minor Violations

Violations found but below critical threshold. Engineering remediation required; peer review of fixes before re-scan.

Engineering remediation

🔴

Critical / Serious Violations

Legal exposure under Section 508, EN 301 549, or ADA. Management escalation and a formal remediation plan required.

Management escalation

Swim Safety Principle

The AI can detect that a form element has no label and score the evidence package 87/100. It cannot determine whether that barrier blocks a specific user from completing a legally required transaction. Conformance claims and governance sign-offs always require a named human owner. This is the P02 boundary encoded in the accessibility quality engine.

What's Next: Automate Ongoing Accessibility Governance

Your evidence package shows the current state. To run this continuously, the SysWisdom AI Quality Agent runs the same journey in Docker on your own machine, behind your firewall. Scans, results and evidence stay private to you.

Continuous governance

Start the AI Quality Agent, reachable only from this machine, then open http://localhost:8080/accessibility or call the API below.

docker run -d --name ai-quality-agent \
  -p 127.0.0.1:8080:8080 \
  -e ACCESSIBILITY_SCAN_ENABLED=true \
  ai-quality-agent:wisdom-v1-customer

Launch a WCAG 2.2 axe-core scan, poll for results, then build the gap report.

# 1. Launch scan
curl -X POST http://localhost:8080/accessibility/scan/launch \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/checkout"}'
# → {"job_id": "abc123", "status": "running"}

# 2. Poll until succeeded
curl http://localhost:8080/accessibility/scan/status/abc123

# 3. Build gap report (technical and governance, kept separate)
curl -X POST http://localhost:8080/accessibility/gap-report \
  -H "Content-Type: application/json" \
  -d '{"assessment_id": "abc123", "evidence": {"vpat_acr": true, "governance_owner": false}}'

Compare a baseline assessment to a new scan to verify and quantify remediation progress.

curl -X POST http://localhost:8080/accessibility/verify \
  -H "Content-Type: application/json" \
  -d '{
    "baseline_assessment_id": "abc123",
    "current_url": "https://example.com/checkout",
    "current_evidence": {
      "vpat_acr": true,
      "accessibility_statement": true,
      "governance_owner": true,
      "governance_owner_name": "Jane Smith"
    }
  }'
# Returns: trend ("improving"|"regressing"|"no change"),
# violations resolved/introduced, governance gaps closed/still open,
# evidence score delta with specific evidence for the trend judgment

Generate a full 8-section evidence package for procurement or internal governance.

curl -X POST http://localhost:8080/accessibility/generate-evidence-package \
  -H "Content-Type: application/json" \
  -d '{
    "assessment_id": "abc123",
    "baseline_assessment_id": "baseline456",
    "save_to_file": true
  }'
# Writes: reports/accessibility_evidence_package_abc123.json
# Sections: executive_summary · technical_accessibility_findings
#           evidence_inventory · governance_documentation_review
#           ai_quality_scorecard · gap_analysis
#           improvement_recommendations · improvement_history

Scan. Evaluate. Document. Prove. Your WCAG 2.2 Accessibility Evidence Journey