verified_user
Standardful
Homechevron_rightStandardschevron_rightWCAG 2.2
Active (Voluntary Framework)International Standardupdate Standard Updated: December 2024fact_check Fact checked: Jun 28, 2026

WCAG 2.2

Web Content Accessibility Guidelines (WCAG) 2.2 — W3C Recommendation (also ISO/IEC 40500:2025)

apartmentPublishing Organization:World Wide Web Consortium (W3C)

Standard Introduction

WCAG 2.2 is an active (voluntary framework) standard published by World Wide Web Consortium (W3C). It is commonly used across Technology, Government, Services, Education, Retail, Finance & Banking and applies in Global.

Use this page to review the official documentation, current status, and the certification or assessment bodies most commonly associated with WCAG 2.2.

Implementation Roadmap

1
Phase 1schedule Duration: 3-6 weeks

Define web accessibility conformance scope

Identify the products, services, systems, entities, jurisdictions, teams, vendors, data flows, and stakeholders covered by WCAG 2.2. Confirm owners, boundaries, applicable obligations, documentation, and evidence expectations for perceivable, operable, understandable, and robust accessibility requirements, success criteria, conformance level, page and app scope, keyboard access, focus appearance, target size, input assistance, testing, exceptions, and regression monitoring.

2
Phase 2schedule Duration: 4-10 weeks

Assess obligations and gaps

Compare current practices with the expected web accessibility conformance approach. Review accessibility requirements, design-system controls, semantic HTML, keyboard and focus behavior, color and contrast checks, forms and error handling, assistive-technology testing, content governance, issue tracking, procurement clauses, and release gates, then prioritize gaps by legal exposure, user or safety impact, customer commitments, operational dependency, reporting deadlines, and assurance readiness.

3
Phase 3schedule Duration: 8-24 weeks

Implement controls and evidence

Deploy required procedures, technical controls, review gates, training, supplier workflows, reporting paths, and operational records. Maintain accessibility inventories, WCAG test results, issue tickets, remediation evidence, design-system documentation, content review logs, assistive-technology test notes, accessibility conformance reports, procurement records, and monitoring reports as traceable evidence.

4
Phase 4schedule Duration: Ongoing

Review, report, and improve

Run management reviews, internal checks, technical testing or independent assessments where applicable, corrective actions, and change reviews. Refresh the program when products, vendors, laws, incidents, reporting cycles, or stakeholder expectations change.

Compliance Checklist

0 / 12

checklist Scope and accountability

checklist Controls and records

checklist Monitoring and assurance

Frequently Asked Questions

Who needs WCAG 2.2?

expand_more

WCAG 2.2 is most relevant to organizations that design, build, procure, or operate websites, web applications, mobile web experiences, and digital content subject to accessibility expectations. The exact scope depends on products, services, jurisdictions, reporting duties, customer commitments, technical requirements, and the organization's role in the relevant ecosystem.

Is WCAG 2.2 certifiable?

expand_more

WCAG 2.2 is a technical accessibility standard and ISO/IEC 40500:2025, not a certification scheme. Organizations demonstrate conformance through testing, remediation, accessibility statements, procurement evidence, and monitoring.

What should implementation focus on first?

expand_more

Start by defining scope, obligations, accountable owners, and the evidence expected by regulators, customers, auditors, assurance providers, or governance bodies. Then perform a gap assessment against current controls and prioritize remediation by risk and deadline.

What evidence is useful for WCAG 2.2?

expand_more

Useful evidence includes accessibility inventories, WCAG test results, issue tickets, remediation evidence, design-system documentation, content review logs, assistive-technology test notes, accessibility conformance reports, procurement records, and monitoring reports. Evidence should be version-controlled, attributable to owners, linked to obligations and controls, and retained for the required review or audit period.

How often should the program be reviewed?

expand_more

Review it at planned intervals and whenever laws, products, vendors, incidents, reporting cycles, customer commitments, technical standards, or assurance expectations change. Higher-risk obligations should have more frequent monitoring and management reporting.

Official Documentation

View All

Related Categories