Category: Standards and Guidelines

Web Content Accessibility Guidelines

Also known as: WCAG, WCAG 2.0, WCAG 2.1, WCAG 2.2

Simply put

The Web Content Accessibility Guidelines (WCAG) are a set of internationally recognized guidelines that describe how to make web content more accessible to people with disabilities. Published by the World Wide Web Consortium (W3C), they are organized around four principles: content should be perceivable, operable, understandable, and robust. WCAG is frequently used as a reference point for evaluating digital accessibility, though meeting its criteria does not by itself guarantee an accessible experience for every user or immunity from legal claims.

Formal definition

WCAG is a technical standard developed by the W3C through its Web Accessibility Initiative (WAI) that defines how to make web content more accessible to people with disabilities. Its guidelines are structured under four foundational principles, Perceivable, Operable, Understandable, and Robust (POUR), with testable success criteria assigned to conformance levels A, AA, and AAA; Level AA is the level most commonly cited as a target. The standard has evolved through successive versions: WCAG 2.0 (published December 11, 2008), WCAG 2.1, and WCAG 2.2, with later versions adding success criteria to the prior baseline (for example, WCAG 2.2 is organized under 13 guidelines). WCAG addresses dynamic content, multimedia, mobile web, and web-based interfaces. WCAG is a technical guideline rather than a law; it is often referenced in regulations, agency guidance, and settlements as a benchmark, but its relationship to specific legal obligations varies by jurisdiction and evolves through rulemaking and case law, readers should consult qualified legal counsel for compliance determinations. Automated testing detects only a portion of possible issues, so manual and assistive technology testing are also required to assess conformance.

Why it matters

WCAG has become the most widely referenced framework for evaluating digital accessibility. Because it is published by the W3C through its Web Accessibility Initiative and is internationally recognized, it provides a common technical vocabulary that regulators, courts, procurement teams, and developers can use to describe what accessible web content looks like. Its four principles, perceivable, operable, understandable, and robust, give organizations a structured way to assess whether people with disabilities can actually access and use their content.

WCAG matters in a legal context because it is frequently cited as a benchmark in regulations, agency guidance, and settlements, even though WCAG is itself a technical guideline rather than a law. The specific relationship between WCAG and any particular legal obligation varies by jurisdiction and continues to evolve through rulemaking and case law, so organizations should not assume that referencing a WCAG version automatically satisfies a legal requirement. Readers facing compliance decisions should consult qualified legal counsel rather than relying on WCAG conformance alone.

Equally important, meeting WCAG success criteria does not by itself guarantee an accessible experience for every user or immunity from legal claims. Automated testing detects only a portion of possible issues, so manual review and testing with assistive technologies remain necessary. Treating WCAG as a floor for good practice, rather than a guarantee, helps organizations build content that is genuinely usable while managing risk realistically.

Who it's relevant to

Accessibility engineers and developers

WCAG provides the testable success criteria that engineers use to build and validate accessible interfaces. Because the criteria are organized under the POUR principles and split across A, AA, and AAA levels, developers need to know which version and level their organization is targeting, commonly Level AA, and should combine automated checks with manual and assistive technology testing to catch issues tools miss.

UX and content designers

Designers rely on WCAG to inform decisions about perceivable and understandable content, including how information is presented across dynamic content, multimedia, and mobile web. Understanding how criteria were added across WCAG 2.0, 2.1, and 2.2 helps design teams plan for evolving expectations rather than treating a single version as static.

Compliance officers and legal counsel

WCAG is frequently referenced in regulations, agency guidance, and settlements as a benchmark, but it is a technical guideline rather than a law, and its relationship to specific legal obligations varies by jurisdiction and evolves through case law and rulemaking. Compliance teams should treat WCAG conformance as a risk-management measure rather than a guarantee of legal safety and should seek qualified legal counsel for compliance determinations.

Business leaders and procurement teams

Because WCAG is an internationally recognized reference point, leaders can use it to set consistent expectations for vendors, contracts, and internal products. Leaders should understand that meeting WCAG criteria does not by itself ensure an accessible experience for every user or immunity from claims, and that ongoing testing and evaluation are part of maintaining accessibility over time.

Inside WCAG

Four Guiding Principles (POUR)

WCAG is organized around four principles stating that content must be Perceivable, Operable, Understandable, and Robust. These principles provide the conceptual foundation under which all guidelines and success criteria are grouped.

Guidelines

Under each principle sit broader guidelines that describe general goals for making content accessible. The guidelines themselves are not testable but frame the more specific success criteria.

Success Criteria

Testable statements used to determine conformance. Each success criterion is assigned a conformance level (A, AA, or AAA). Some criteria were introduced in later versions, so practitioners should confirm which version a given criterion belongs to.

Conformance Levels (A, AA, AAA)

Three levels indicating the degree of conformance. Level A represents the most basic requirements, AA adds further criteria, and AAA is the most stringent. Level AA is the level most commonly cited as a target in policies and settlements.

Versions (WCAG 2.0, 2.1, 2.2)

WCAG has been published in successive versions by the W3C through the Web Accessibility Initiative. Later versions generally add success criteria (for example addressing mobile, touch, and low-vision needs) while remaining backward compatible with earlier versions.

Supporting Documents

The W3C publishes accompanying materials such as techniques and understanding documents that explain how to meet success criteria. These are guidance rather than normative requirements themselves.

Common questions

Answers to the questions practitioners most commonly ask about WCAG.

Does the ADA legally require conformance to a specific version of WCAG?

Not in the sense of a codified technical rule. The ADA is a US civil rights law and does not itself contain detailed web technical specifications. That said, courts, settlements, and some agency guidance have frequently referenced WCAG, most commonly Level AA, as a benchmark for accessibility. Whether a specific WCAG version applies in a given situation typically depends on the applicable authority (for example, Title II or Title III of the ADA), any relevant regulation or agency guidance, and the terms of specific settlements. Because these expectations evolve through regulation and case law, you should consult qualified legal counsel and current agency rulemaking for your circumstances. This entry is not legal advice.

If our site passes automated accessibility checks and meets WCAG success criteria, are we fully accessible and safe from legal claims?

Not necessarily. Meeting WCAG success criteria is a conformance measure and does not guarantee an accessible experience for every user, nor does it guarantee immunity from legal claims. Automated testing detects only a portion of potential issues; manual review and testing with assistive technologies are generally needed to evaluate real-world usability. Conformance, usability, and legal compliance are related but distinct, and legal exposure depends on facts, jurisdiction, and evolving case law. Consult qualified legal counsel regarding your specific risk.

Which WCAG conformance level should we target?

Level AA is the level most commonly cited as a target in accessibility guidance, settlements, and organizational policies, as it balances comprehensiveness with feasibility. Level A represents the most basic requirements, while Level AAA includes the most stringent criteria that are often not achievable across all content. Many organizations adopt WCAG Level AA as a working standard, but you should confirm the appropriate target against any authority, regulation, or agency guidance that applies to your context.

Which WCAG version should we work toward?

WCAG has been published in successive versions, 2.0, 2.1, and 2.2, with later versions adding success criteria, particularly around mobile, low vision, and cognitive accessibility, while remaining backward compatible. Later versions generally build on earlier ones rather than replacing their criteria. Selecting a version often depends on the standard referenced by any applicable regulation, guidance, or contractual obligation, so verify which version applies to your situation before setting it as your target.

How should we test our content against WCAG?

A combination of methods is generally recommended. Automated tools can efficiently flag certain issues but detect only a portion of potential problems. Manual review by knowledgeable evaluators and testing with assistive technologies, such as screen readers, keyboard-only navigation, and magnification, are needed to assess criteria that automation cannot reliably check. Testing with people who use assistive technology can further surface usability issues that conformance checks may miss.

Do the WCAG guidelines apply to more than just web pages?

WCAG is organized around four principles, that content be perceivable, operable, understandable, and robust, and is written to be applied broadly to web content. Its guidance is often referenced for web-based documents, applications, and other digital content, and related W3C and Access Board resources address contexts such as non-web documents and software. Because scope and applicable requirements depend on the authority and standard governing your situation, confirm how WCAG maps to your particular content and platform.

Common misconceptions

The ADA legally requires a specific version of WCAG.

The ADA is a US civil rights law and does not itself contain detailed web technical specifications. Courts and settlements have often referenced WCAG as a benchmark rather than a codified rule. Any specific version requirement should be attributed to a particular settlement, regulation, or agency guidance, and readers should consult qualified legal counsel and current rulemaking.

Meeting WCAG success criteria or passing automated checks guarantees an accessible experience and legal immunity.

Conformance, usability, and legal compliance are distinct. Automated testing detects only a portion of issues, and manual and assistive technology testing are required. Meeting success criteria does not guarantee an accessible experience for all users nor immunity from legal claims.

All WCAG success criteria are the same across versions and levels.

Success criteria differ by version and conformance level. Some criteria were added in WCAG 2.1 or 2.2 and are not present in 2.0, and each criterion is assigned to a specific level (A, AA, or AAA). Conflating them can lead to inaccurate conformance claims.

Best practices

Identify and document the specific WCAG version and conformance level you are targeting (Level AA is most commonly cited), and confirm which success criteria belong to that version.

Combine automated testing with manual review and assistive technology testing, since automated tools detect only a portion of accessibility issues.

Treat WCAG conformance as one input among several, distinguishing it from real-world usability and from legal compliance.

Consult the W3C's supporting techniques and understanding documents to clarify how to meet each success criterion.

Determine which legal authority applies to your context (for example Section 508 for federal agencies, ADA Title II for state and local government, ADA Title III for public accommodations) and consult qualified legal counsel for compliance decisions.

Monitor current agency rulemaking and case law, as expectations referencing WCAG evolve over time and this guidance is not legal advice.