Purpose of the Template
This checklist provides a structured format for tracking WCAG 2.2 conformance across your organization. It helps document current status, assign accountability, and demonstrate progress toward full compliance. This work will be foundational when WCAG 3.0 is introduced.
You need this now because WCAG 2.2 defines your current legal obligations. The DOJ Final Rule (2024) references WCAG 2.1 Level AA. ADA Title III litigation points to WCAG 2.x. The European Accessibility Act relies on EN 301 549, which references WCAG 2.x. None of these reference WCAG 3.0.
The W3C states that content conforming to WCAG 2.2 Levels A and AA is expected to meet most of WCAG 3's minimum conformance requirements. Your WCAG 2.2 work is foundational for WCAG 3.
Prerequisites
Before using this template, ensure you have:
- A baseline audit. Understand your current conformance level by running automated scans and manual testing against WCAG 2.2 Level AA.
- Asset inventory. List all digital properties in scope: public website, customer portal, mobile apps, internal tools, and third-party integrations.
- Clear ownership. Identify who is accountable for each property. This may not always be the team that built it.
- Remediation capacity. Determine whether issues will be fixed in-house, through vendors, or both.
If you haven't completed a baseline audit, start there. This checklist assumes you've identified the gaps.
The Template
Copy this into your compliance documentation system. Customize the asset list and success criteria based on your audit findings.
WCAG 2.2 CONFORMANCE TRACKING CHECKLIST
Organization: [Your organization name]
Audit date: [Date]
Target conformance level: Level AA
Next review: [Date]
ASSET INVENTORY
Asset name | Owner | Platform | In scope? | Audit complete? | Conformance status
-----------|-------|----------|-----------|-----------------|-------------------
[Example: Public website] | [Team/vendor] | [CMS] | Yes | Yes | Partial
[Example: Customer portal] | [Team/vendor] | [Platform] | Yes | No | Unknown
[Example: Mobile app - iOS] | [Team/vendor] | Native | Yes | Yes | Non-conformant
LEVEL A SUCCESS CRITERIA (25 total)
Criterion | Asset | Status | Owner | Target date | Validation method | Notes
----------|-------|--------|-------|-------------|-------------------|------
1.1.1 Non-text Content | Public website | Pass | Content team | N/A | Manual review | All images have alt text
1.2.1 Audio-only and Video-only | Customer portal | Fail | Marketing | Q2 2025 | [Screen reader testing](/glossary/screen-reader-testing) | Product demo video missing [transcript](/glossary/transcript)
1.3.1 Info and Relationships | Public website | Fail | Dev team | Q1 2025 | Automated + manual | Form labels missing on contact form
1.4.1 Use of Color | Mobile app | Fail | Product team | Q2 2025 | Manual review | Error states use color only
[Continue for all Level A criteria]
LEVEL AA SUCCESS CRITERIA (20 total)
Criterion | Asset | Status | Owner | Target date | Validation method | Notes
----------|-------|--------|-------|-------------|-------------------|------
1.4.3 Contrast (Minimum) | Public website | Fail | Design team | Q1 2025 | Automated scan | 47 instances below 4.5:1
1.4.5 [Images of Text](/glossary/images-of-text) | Customer portal | Pass | Content team | N/A | Manual review | No images of text used
2.4.5 Multiple Ways | Public website | Pass | UX team | N/A | Manual review | Search and sitemap present
3.1.2 Language of Parts | Public website | Fail | Content team | Q1 2025 | Manual review | Spanish quotes not marked with lang attribute
[Continue for all Level AA criteria]
WCAG 2.2-SPECIFIC CRITERIA (9 new in 2.2)
Criterion | Asset | Status | Owner | Target date | Validation method | Notes
----------|-------|--------|-------|-------------|-------------------|------
2.4.11 Focus Not Obscured (Minimum) | Public website | Fail | Dev team | Q1 2025 | Keyboard testing | Modal overlay obscures focused element
2.4.12 Focus Not Obscured (Enhanced) | Public website | Not tested | Dev team | Q2 2025 | Keyboard testing | Level AAA - not required
2.5.7 Dragging Movements | Mobile app | Pass | Product team | N/A | Manual testing | Drag-to-reorder has single-pointer alternative
2.5.8 Target Size (Minimum) | Public website | Fail | Design team | Q1 2025 | Manual measurement | Icon buttons below 24x24 CSS pixels
3.2.6 [Consistent Help](/glossary/consistent-help) | Customer portal | Fail | UX team | Q2 2025 | Manual review | Help link position varies across pages
3.3.7 [Redundant Entry](/glossary/redundant-entry) | Customer portal | Fail | Dev team | Q1 2025 | Manual testing | Shipping address not auto-populated from billing
3.3.8 [Accessible Authentication](/glossary/accessible-authentication) (Minimum) | Customer portal | Pass | Security team | N/A | Manual testing | Password manager compatible
3.3.9 Accessible Authentication (Enhanced) | Customer portal | Not tested | Security team | Q3 2025 | Manual testing | Level AAA - not required
CONFORMANCE SUMMARY
Total success criteria applicable: [Number]
Criteria passed: [Number]
Criteria failed: [Number]
Not yet tested: [Number]
Conformance percentage: [Number]%
NEXT ACTIONS
Priority 1 (blocks core user journeys):
- [Example: Fix keyboard trap in checkout flow - blocks purchase completion]
- [Example: Add form labels to login page - blocks account access]
Priority 2 (significant barriers):
- [Example: Fix contrast failures on navigation - affects all pages]
- [Example: Add transcripts to product videos - affects product research]
Priority 3 (lower-impact issues):
- [Example: Mark language changes in blog posts]
- [Example: Increase target size on footer links]
LEGAL COMPLIANCE NOTES
Applicable regulations: [Example: ADA Title III, Section 508, European Accessibility Act]
Reference standard: WCAG 2.2 Level AA
Last legal review: [Date]
Next compliance audit: [Date]
Customizing the Template
Asset inventory: List every digital property you're responsible for. Include third-party tools if users access them through your interface. If you sell software, include customer-facing configuration screens.
Success criteria rows: The template shows examples. Add a row for every WCAG 2.2 success criterion that applies to your content. The full list is in the WCAG 2.2 specification.
Status values: Use consistent labels: Pass, Fail, Partial (some instances pass, some fail), Not Applicable, Not Tested.
Validation method: Document how you verified each criterion. Automated scans catch some issues; manual testing catches others. Screen reader testing is essential for interactive elements. Keyboard-only navigation testing is required for all interactive content.
Priority assignment: Don't treat all failures equally. A keyboard trap in your checkout flow has more immediate impact than a missing language attribute on a decorative quote. Your remediation plan should reflect this.
Target dates: Be realistic. If you have 200 contrast failures, you won't fix them all by next week. Set dates you can defend in a legal review.
Validation Steps
Once you've customized the template:
Cross-check against your audit report. Every failure in your audit should appear in this checklist. If it doesn't, you're not tracking it.
Verify owner assignments. Confirm that each owner knows they're accountable. An unassigned row is a gap that won't get fixed.
Test your validation methods. If you marked something "Pass" based on an automated scan, spot-check it manually. Automated tools miss context-dependent failures.
Review with legal or GRC. Show them the conformance percentage and the priority rankings. They need to know where the risk sits.
Schedule the next review. Conformance isn't static. New content introduces new failures. Set a recurring review; quarterly is common for active properties.
Document assumptions. If you marked a criterion "Not Applicable," note why. If your site has no audio content, 1.2.1 doesn't apply, but document that decision in case you add a podcast later.
This checklist won't make you conformant by itself. It gives you a structure for tracking the work and proving you're making progress. As WCAG 3.0 approaches, you'll already have the foundation in place.
