guide
WCAG 2.2 for government: requirements, priorities, and audit checklist
WCAG 2.2 compliance for public-sector sites requires applying Web Content Accessibility Guidelines 2.2 to the specific failure points typical of the government industry — including inaccessible pdf forms and notices, inaccessible kiosks and ticketing terminals, outdated cms platforms.
Does WCAG 2.2 apply to public-sector sites?
WCAG 2.2 (pronounced 'wuh-cag 2.2') is the World Wide Web Consortium's globally adopted standard for web accessibility, published October 2023, defining 87 testable success criteria organised under four principles: Perceivable, Operable, Understandable, Robust.
Government accessibility — the lay of the land
Public-sector compliance is layered: technical standards (Section 508, EN 301 549), legal mandates (ADA, WAD, ACA), and procurement rules (VPAT/ACR requirements). State and local governments now face the April 2024 DOJ final rule with compliance dates of April 2026/2027.
Where WCAG 2.2 bites hardest in public-sector sites
• Inaccessible PDF forms and notices
• Inaccessible kiosks and ticketing terminals
• Outdated CMS platforms
• Procurement of inaccessible third-party services
• Lack of accessibility staff in smaller agencies
Remediation priorities
• Online services and benefits portals
• PDF forms and notices
• Tax, licensing, permitting flows
• Public meeting and election information
• Kiosks and self-service terminals
How to comply with WCAG 2.2 on a Government site
1. Establish scope and baseline: Inventory every public-facing digital property. Run an automated baseline scan to detect the ~25–30% of WCAG criteria that machines can reliably check.
2. Manual + assistive-technology audit: Engage IAAP-credentialed auditors to test the remaining ~70% of criteria — keyboard, screen reader (NVDA, JAWS, VoiceOver), zoom and cognitive criteria.
3. Remediate at source: Fix issues in source code, not via overlay widgets. Train developers; integrate axe-core into CI; track open issues in JIRA or Linear.
4. Publish an accessibility statement: Disclose conformance level, known limitations, contact for accessibility feedback, and remediation timelines. Required under EAA and best-practice under ADA.
5. Monitor and re-test: Re-audit quarterly. Re-test before every major release. Keep an internal VPAT/ACR current and post it publicly.
Sources
- Web Content Accessibility Guidelines (WCAG) 2.2 — W3C
- WCAG 2 Overview — W3C WAI
- What's New in WCAG 2.2 — W3C WAI
- Test Evaluating Web Accessibility — W3C WAI
- Section508.gov — GSA
- ADA Title II Rule — US DOJ
FAQ
Frequently asked questions
Cited answers. Sourced. Updated as standards and case law change.
Does WCAG 2.2 apply to government websites?
WCAG 2.2 (pronounced 'wuh-cag 2.2') is the World Wide Web Consortium's globally adopted standard for web accessibility, published October 2023, defining 87 testable success criteria organised under four principles: Perceivable, Operable, Understandable, Robust.
What are the most common WCAG 2.2 failures in public-sector sites?
Inaccessible PDF forms and notices Inaccessible kiosks and ticketing terminals Outdated CMS platforms
What conformance level should a government site target?
WCAG 2.2 Level AA is the consensus target for legal compliance and the level referenced by virtually every national accessibility law.
What does the DOJ Title II final rule require?
WCAG 2.1 Level AA conformance for web content, mobile apps, kiosks, and self-service terminals operated by state and local government entities. Compliance deadlines: April 2026 for entities serving >50,000 residents; April 2027 for smaller.
How does Section 508 differ from ADA Title II?
Section 508 governs federal procurement of ICT and applies to vendors selling to federal buyers. ADA Title II governs state and local government services. Both reference WCAG. A federal contractor often complies with both simultaneously via a single VPAT.
Stop guessing. Get the audit a Fortune 500 a11y team would have written.
Free audit on your live URL. No sign-up. IAAP-format report. Ready in hours.
founders@accessivepath.com · +977 9851094056