Skip to main content
Accessibility.com, LLC
Category: Standards and Guidelines

WCAG 2.1

Also known as: WCAG 2.1, Web Content Accessibility Guidelines 2.1
Simply put

WCAG 2.1 is a set of technical guidelines that explain how to make web content more accessible to people with disabilities. Published by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative (WAI), it builds on the earlier WCAG 2.0 and is designed to be broadly applicable to a range of web technologies, including dynamic applications and mobile. Following these guidelines can help improve accessibility, though conformance alone does not guarantee an accessible experience for every user or legal compliance.

Formal definition

WCAG 2.1 is a W3C guideline document, published through the Web Accessibility Initiative (WAI), that defines how to make web content more accessible to people with disabilities through testable success criteria. It extends WCAG 2.0 and is designed to be backwards compatible, meaning content conforming to a later version such as WCAG 2.2 also conforms to WCAG 2.1 and WCAG 2.0. Its success criteria are organized under conformance levels (A, AA, and AAA), with AA commonly cited as a target, and are intended to be broadly applicable to current and future web technologies, including dynamic applications and mobile. Meeting these success criteria typically requires a combination of automated, manual, and assistive technology testing, as automated tools detect only a portion of potential issues. This entry is informational and not legal advice; accessibility requirements evolve through regulation and case law, and qualified legal counsel should be consulted for compliance questions.

Why it matters

WCAG 2.1 provides a shared, testable framework for making web content more accessible to people with disabilities. Because it is published by the W3C through the Web Accessibility Initiative and is widely recognized across the accessibility field, it gives organizations a common reference point for evaluating and improving digital content. The AA conformance level is commonly cited as a target in accessibility programs and is frequently referenced in settlements and agency guidance as a benchmark, though the guidelines themselves are technical standards rather than a law.

WCAG 2.1 matters because it extends WCAG 2.0 to address technologies and use cases that have become central to how people interact with the web, including dynamic applications and mobile. This broader applicability helps organizations account for a wider range of user needs and interaction methods than the earlier version alone. Because WCAG 2.0, 2.1, and 2.2 are designed to be backwards compatible, content that conforms to a later version also conforms to WCAG 2.1, which helps organizations plan for evolving standards without discarding prior work.

It is important to understand the limits of conformance. Meeting WCAG 2.1 success criteria does not by itself guarantee an accessible experience for every user, and it does not guarantee legal compliance or immunity from claims. Accessibility requirements evolve through regulation and case law, and this entry is informational rather than legal advice; organizations with compliance questions should consult qualified legal counsel and monitor current agency rulemaking.

Who it's relevant to

Accessibility engineers and developers
WCAG 2.1 gives engineers and developers concrete, testable success criteria to build against, including guidance relevant to dynamic applications and mobile. Because automated tools catch only some issues, practitioners generally combine automated checks with manual and assistive technology testing to evaluate conformance.
UX and content designers
Designers can use WCAG 2.1 as a reference when creating interfaces and content, with AA commonly used as a working target. Meeting success criteria supports a more accessible experience, though designers should remember that conformance alone does not guarantee usability for every user.
Compliance officers and business leaders
WCAG 2.1, particularly at AA, is frequently cited as a benchmark in accessibility programs. Leaders can use it to set consistent internal standards, while recognizing that conformance does not by itself ensure legal compliance and that requirements evolve through regulation and case law.
Legal counsel
Counsel may encounter WCAG 2.1 referenced as a benchmark in settlements or agency guidance rather than as a codified legal rule. Because the applicability and interpretation of these guidelines depend on jurisdiction and evolving case law, this entry should not be treated as legal advice.

Inside WCAG 2.1

Foundation in WCAG 2.0
WCAG 2.1 was published by the W3C through the Web Accessibility Initiative (WAI) as an extension of WCAG 2.0. It retains all of the success criteria from WCAG 2.0 and adds new ones, so content conforming to WCAG 2.1 also generally conforms to WCAG 2.0 at the same level.
Four Guiding Principles (POUR)
Like earlier versions, WCAG 2.1 organizes its guidelines under four principles: Perceivable, Operable, Understandable, and Robust. Each principle contains guidelines, and each guideline is supported by testable success criteria.
Conformance Levels A, AA, and AAA
Success criteria are assigned to three conformance levels. Level AA is the level most commonly cited as a target in policies, settlements, and agency guidance, while AAA represents the most stringent and is generally not required across an entire site.
New Success Criteria Added in 2.1
WCAG 2.1 introduced additional success criteria beyond WCAG 2.0, with an emphasis on improving accessibility for users on mobile devices, users with low vision, and users with cognitive or learning disabilities. These criteria are distributed across the A, AA, and AAA levels.
Testable Success Criteria
Each success criterion is written to be testable, though testing may require a combination of automated tools, manual review, and assistive technology evaluation. Automated tools detect only a portion of potential issues.

Common questions

Answers to the questions practitioners most commonly ask about WCAG 2.1.

Does the ADA legally require WCAG 2.1 conformance?
Not by its own text. The Americans with Disabilities Act is a US civil rights law and does not itself contain detailed web technical specifications naming WCAG 2.1. WCAG 2.1 is a technical standard published by the W3C through the Web Accessibility Initiative, and it has often been referenced by courts, settlements, and agency guidance as a benchmark rather than being codified as a universal legal mandate. Whether a specific WCAG version applies to your organization can depend on the particular regulation, settlement, or agency guidance involved, so you should consult qualified legal counsel and monitor current rulemaking. This entry is not legal advice.
If our site conforms to WCAG 2.1 Level AA, does that guarantee it is accessible and legally compliant?
No. Meeting WCAG 2.1 success criteria does not guarantee an accessible experience for every user, nor does it guarantee immunity from legal claims. Conformance, usability, and legal compliance are distinct. Automated testing detects only a portion of potential issues, so manual review and testing with assistive technologies are generally needed to evaluate real-world accessibility. Conformance is commonly cited as a strong and defensible target, but it should be treated as part of an ongoing effort rather than a one-time guarantee.
What is the difference between WCAG 2.0, 2.1, and 2.2, and which should we target?
WCAG 2.1 builds on WCAG 2.0 by adding success criteria while retaining all of the earlier ones, so conforming to 2.1 also means conforming to the corresponding 2.0 requirements. WCAG 2.2 further builds on 2.1 in the same additive manner. The added criteria in 2.1 address needs such as mobile, low-vision, and cognitive accessibility. Level AA is the conformance level most commonly cited as a target. Which version and level are appropriate for your organization may depend on applicable guidance, contractual requirements, and case law, so confirm the current expectations for your context.
How do we know which WCAG 2.1 success criteria are Level A versus Level AA?
Each WCAG 2.1 success criterion is assigned a conformance level of A, AA, or AAA, and this designation is published in the W3C guidelines themselves. To claim a given level, you must satisfy all criteria at that level and the levels below it, so AA conformance requires meeting both A and AA criteria. Because some criteria were introduced in WCAG 2.1 rather than 2.0, refer directly to the official W3C documentation for the authoritative level assigned to each criterion rather than relying on memory or secondhand summaries.
Can automated tools confirm WCAG 2.1 conformance?
Automated tools are useful for finding certain classes of issues efficiently, but they detect only a portion of potential accessibility problems and cannot on their own confirm full WCAG 2.1 conformance. Many success criteria require human judgment, such as evaluating whether alternative text is meaningful or whether content order makes sense. A thorough evaluation generally combines automated scanning with manual review and testing using assistive technologies such as screen readers.
How should we document our WCAG 2.1 conformance efforts?
Organizations commonly document conformance through an accessibility conformance report, and structured formats are often used to record how each applicable success criterion is addressed. Documentation may capture the WCAG version and conformance level evaluated, the testing methods used including manual and assistive technology testing, and known limitations or remediation plans. Keeping such records current is generally advisable because requirements evolve through regulation and case law, and documentation should not be treated as a substitute for ongoing testing or as legal advice.

Common misconceptions

WCAG 2.1 is legally mandated by the ADA.
The Americans with Disabilities Act is a US civil rights law and does not itself codify a specific WCAG version. WCAG 2.1 (commonly at Level AA) is often referenced as a benchmark in settlements, agency guidance, and some regulations, but any specific legal requirement should be attributed to the particular authority and confirmed with qualified legal counsel, as requirements evolve through regulation and case law.
Conforming to WCAG 2.1 guarantees an accessible experience and legal immunity.
Meeting WCAG 2.1 success criteria does not guarantee that all users will have an accessible experience, nor does it guarantee immunity from legal claims. Conformance, usability, and legal compliance are distinct. Manual testing and assistive technology testing remain necessary alongside automated checks.
WCAG 2.1 replaces WCAG 2.0 and is unrelated to WCAG 2.2.
WCAG 2.1 builds on WCAG 2.0 rather than replacing it, retaining all 2.0 criteria and adding new ones. WCAG 2.2 similarly extends 2.1. Each version is backward compatible, so practitioners should confirm which version and level applies to their specific obligation.

Best practices

Identify which WCAG version and conformance level applies to your context, and confirm the source of that requirement (regulation, settlement, or agency guidance) rather than assuming the ADA specifies a version.
Target Level AA as a commonly cited baseline while treating specific obligations as version- and jurisdiction-dependent.
Combine automated testing with manual review and assistive technology testing, since automated tools detect only a portion of accessibility issues.
Pay particular attention to the success criteria added in WCAG 2.1 that address mobile use, low vision, and cognitive or learning disabilities, as these may not be covered by tools calibrated to WCAG 2.0.
Document your conformance efforts and testing methodology, recognizing that conformance is distinct from usability and from legal compliance.
Consult qualified legal counsel and monitor current agency rulemaking and case law, since accessibility requirements continue to evolve.