Category: WCAG Principles and Conformance

Conformance Claim

Also known as: WCAG Conformance Claim

Simply put

A conformance claim is a voluntary, public statement in which an organization declares that a website or piece of web content meets a specified level of the Web Content Accessibility Guidelines (WCAG). Making such a claim is optional, so content can conform to WCAG without any claim being published. When an organization does make a claim, WCAG expects it to include certain required information and allows some optional details.

Formal definition

Under WCAG, a conformance claim is a formal, voluntary declaration that specified web content satisfies all of the applicable success criteria at a stated conformance level (A, AA, or AAA). WCAG explicitly states that making a conformance claim is not required in order to conform; however, if a claim is made, it must include all required components as defined in the standard's conformance section (for example, the date, the WCAG version and level claimed, a description of the content covered, and the technologies relied upon). WCAG also defines optional components that may be included. A conformance claim is a self-declaration of accessibility status against the technical standard; it is distinct from third-party certification, does not itself guarantee an accessible experience for all users, and is separate from legal compliance obligations, which are determined by applicable law, regulation, and case law rather than by WCAG itself. This entry is not legal advice; consult qualified counsel regarding regulatory requirements.

Why it matters

A conformance claim gives organizations a structured way to communicate the accessibility status of their web content against a recognized technical standard. Because WCAG explicitly states that making a claim is not required in order to conform, the presence or absence of a claim does not by itself indicate whether content meets the guidelines. When a claim is made, however, WCAG expects it to carry specific required information, which lends the statement more accountability than a vague marketing assertion of accessibility.

For readers, the distinction matters because a conformance claim is a self-declaration rather than a third-party certification or a legal safe harbor. It reflects an organization's own assessment of how its content measures against the stated success criteria and level. It does not guarantee an accessible experience for every user, and it is separate from legal compliance obligations, which in the United States are shaped by applicable law, regulation, and case law rather than by WCAG itself. A published claim can be useful evidence of accessibility effort, but it should not be treated as proof of either full usability or legal immunity.

Understanding what a valid claim must contain also helps readers evaluate the credibility of accessibility statements they encounter. A claim that omits required components, or that conflates a self-declaration with formal certification, should be read with caution. This entry is informational and is not legal advice; organizations should consult qualified counsel regarding regulatory requirements.

Who it's relevant to

Compliance officers

Compliance officers use conformance claims to document and communicate the accessibility status of digital content. They should understand that a claim is a voluntary self-declaration with required components, not a certification or a guarantee of legal compliance, and that its accuracy depends on the testing behind it.

Accessibility engineers and testers

Engineers and testers are responsible for the evaluation that supports a claim. Because automated checks catch only a portion of issues, they generally need to combine manual review and assistive technology testing before an organization asserts conformance at a stated level.

UX designers and content teams

Designers and content teams need to know the specific version, level, and scope covered by a claim so that the content they produce or update remains within the claimed boundaries and continues to meet the relevant success criteria.

Legal counsel

Counsel should recognize that a WCAG conformance claim is a self-declaration against a technical standard and is separate from legal compliance obligations, which are determined by applicable law, regulation, and case law. A published claim may serve as evidence of accessibility effort but does not by itself confer legal immunity.

Business leaders

Business leaders evaluating whether to publish a conformance claim should weigh its value as a public statement of accessibility effort against the responsibility to keep it accurate and current, and should avoid treating it as a substitute for ongoing testing or legal review.

Inside Conformance Claim

Date of the Claim

A conformance claim commonly includes the date on which the claim is made, since web content and its conformance status can change over time.

Guidelines Title, Version, and URI

The claim should identify the standard it references, such as 'Web Content Accessibility Guidelines 2.1,' along with the version and a link to the guidelines. This distinguishes whether the claim references WCAG 2.0, 2.1, or 2.2.

Conformance Level Satisfied

The claim states the conformance level met, whether A, AA, or AAA. Level AA is the level most commonly cited as a target for many organizations and settlements.

Scope of the Content Covered

A precise description of the web pages or content covered by the claim, typically expressed as a list of URIs. Content not listed is generally not covered by the claim.

Web Content Technologies Relied Upon

A list of the technologies (such as HTML, CSS, or scripting) that the content depends on to meet the claimed conformance level.

Common questions

Answers to the questions practitioners most commonly ask about Conformance Claim.

Does publishing a WCAG conformance claim make my website legally compliant with the ADA?

No. A conformance claim is a statement about meeting specific WCAG success criteria at a stated level; it is not a determination of legal compliance. The ADA is a US civil rights law, and courts and settlements have often referenced WCAG as a benchmark rather than as codified technical requirements. Meeting WCAG success criteria does not guarantee immunity from legal claims. For questions about legal exposure, consult qualified legal counsel and monitor current agency rulemaking and case law.

If my site passes automated testing, can I make a valid conformance claim?

Not on that basis alone. Automated testing detects only a portion of accessibility issues, and passing automated checks does not establish conformance with all applicable success criteria. A defensible conformance claim generally relies on manual evaluation and testing with assistive technologies in addition to automated tools. Conformance also does not by itself guarantee an accessible experience for all users.

What information should a conformance claim include?

A conformance claim generally identifies the WCAG version being claimed, the conformance level (for example, A, AA, or AAA), the date of the claim, and the scope of what was evaluated, such as specific pages, URLs, or a defined set of content. Because WCAG success criteria differ across versions, stating the version and level precisely helps others understand what the claim covers and where its limits lie.

Which WCAG level should a conformance claim target?

Level AA is the level most commonly cited as a target in accessibility practice. When making a claim, be specific about both the version (such as WCAG 2.0, 2.1, or 2.2) and the level, and note that some criteria were added in later versions. This guidance is not legal advice; applicable expectations may vary by jurisdiction and by any relevant regulation, settlement, or agency guidance.

How should scope be defined in a conformance claim?

Scope should describe exactly what content was evaluated, since a claim applies only to the material covered. This can include specific pages, a set of URLs, page states, or defined processes. Content outside the stated scope is not covered by the claim, and dynamic, user-generated, or third-party content may warrant separate consideration.

How often should a conformance claim be reviewed or updated?

Because a conformance claim reflects the state of evaluated content at a point in time, it can become outdated as a site changes. Claims are commonly revisited when content, features, or code are updated, and may also warrant review as WCAG versions evolve. Retesting through manual, assistive technology, and automated methods generally supports keeping a claim current.

Common misconceptions

A conformance claim guarantees an accessible experience for all users and immunity from legal claims.

Meeting WCAG success criteria and publishing a conformance claim does not guarantee usability for every user, nor does it guarantee protection from legal claims. Automated testing detects only a portion of issues, and manual and assistive technology testing are generally required. A claim is a statement of conformance, not a legal safe harbor; readers should consult qualified legal counsel for their situation.

A conformance claim applies to an entire website automatically.

A claim covers only the scope explicitly defined, commonly expressed as a list of URIs. Pages or content not included in the stated scope are generally not covered, and content that changes after the claim date may no longer reflect the claimed status.

The ADA legally requires organizations to publish a WCAG conformance claim at a specific version.

The ADA is a US civil rights law and does not itself codify detailed web technical specifications or mandate publishing a conformance claim. WCAG is a technical guideline published by the W3C, and it is often cited as a benchmark in settlements and agency guidance rather than as a universal codified rule. Any specific requirement should be attributed to the relevant regulation, settlement, or agency guidance.

Best practices

State the specific WCAG version and conformance level being claimed (for example, WCAG 2.1 Level AA), and avoid conflating success criteria across versions.

Define the scope precisely by listing the URIs or content covered, and clearly note what is excluded from the claim.

Include the date of the claim and review it regularly, since content changes may affect the accuracy of the claim over time.

List the web content technologies relied upon to satisfy the claimed level so the basis of conformance is transparent.

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

Avoid framing a conformance claim as a guarantee of legal compliance or full accessibility, and consult qualified legal counsel regarding jurisdiction-specific obligations.