Conformance Claims — Documenting WCAG Compliance

In this tutorial, you will learn about Conformance Claims. We cover key concepts, practical examples, and best practices to help you master this topic.

A WCAG conformance claim is a public statement that a page or set of pages meets specified WCAG requirements, including the version, level, scope, evaluation method, and date of evaluation.

What You'll Learn

You will learn what a conformance claim is, what it must include, how to create one, and common pitfalls to avoid.

Why It Matters

A conformance claim demonstrates transparency and accountability. Courts and procurement officers look for documented conformance claims. Without one, users and buyers cannot verify your Compliance.

Real-World Use

DodaTech publishes a conformance claim for each product. Durga Antivirus Pro's claim specifies WCAG 2.2 AA conformance, scope (web dashboard and reports), evaluation method (WCAG-EM), and last review date.

flowchart TD
  A[Conformance Claim] --> B[Required components]
  A --> C[Optional components]
  A --> D[Where to publish]
  B --> E[WCAG version and level]
  B --> F[Scope of claim]
  B --> G[Evaluation method]
  B --> H[Date of evaluation]
  C --> I[Known limitations]
  C --> J[Contact information]
  D --> K[Accessibility statement page]
  D --> L[Site footer]
  D --> M[Procurement documentation]

Required Components

WCAG Version and Level

Specify which WCAG version (2.0, 2.1, or 2.2) and conformance level (A, AA, or AAA).

Scope

Define which pages, sections, or functionality the claim covers. Scope can be a single page, a set of pages, or an entire site.

Evaluation Method

Describe how conformance was evaluated. Methods include automated testing, manual testing, screen reader testing, user testing, and WCAG-EM.

Date of Evaluation

When the evaluation was completed. Claims should be updated regularly.

Optional Components

Known limitations or exceptions. Contact information for Accessibility feedback. Information about ongoing monitoring.

<!-- Conformance claim in HTML -->
<div aria-label="Accessibility conformance statement">
  <h2>Accessibility Conformance</h2>
  <p>
    Durga Antivirus Pro conforms to
    <a href="https://www.w3.org/TR/WCAG22/">WCAG 2.2</a>
    at Level AA.
  </p>
  <p>
    <strong>Scope:</strong> Web dashboard, settings panels, and report pages.
    Mobile app is covered in a separate claim.
  </p>
  <p>
    <strong>Evaluation method:</strong>
    <a href="https://www.w3.org/WAI/eval/conformance.html">WCAG-EM</a>.
    Automated testing with axe-core, manual keyboard testing, and
    screen reader testing with NVDA and VoiceOver.
  </p>
  <p>
    <strong>Last evaluated:</strong> June 2026.
    <strong>Next evaluation:</strong> September 2026.
  </p>
  <p>
    <a href="/accessibility/feedback">Report an accessibility issue</a>
  </p>
</div>

{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "accessibilityFeature": [
    "alternativeText",
    "longDescription",
    "structuredNavigation"
  ],
  "accessibilityHazard": [
    "noFlashingHazard"
  ],
  "accessibilityAPI": "ARIA",
  "accessibilityControl": [
    "fullKeyboardControl",
    "fullMouseControl"
  ],
  "accessMode": ["textual", "visual"],
  "accessModeSufficient": ["textual", "visual"]
}

Where to Publish

Publish your conformance claim on your accessibility statement page. Link to it from your site footer. Include it in procurement documentation and VPAT.

Common Mistakes

1. No Conformance Claim at All

Without a claim, users and buyers cannot verify your compliance. This is a missed opportunity for trust.

2. Claiming Compliance Without Documentation

A claim without documented evaluation method and scope is not credible. Describe how you evaluated compliance.

3. Using Vague Language

We strive to be accessible is not a conformance claim. A claim must specify version, level, scope, and method.

4. Not Updating the Claim

An outdated claim is worse than no claim. Update it at least annually or after significant changes.

5. Overclaiming Conformance

Claiming AAA when you only meet AA is misleading. Be accurate about your conformance level.

6. Forgetting to List Exceptions

If some content does not meet the claimed level, document it. Exceptions are acceptable with explanation.

7. Not Including Contact Information

Users who encounter barriers need a way to report them. Include contact information for accessibility feedback.

Practice Questions

1. What are the four required components of a conformance claim?

WCAG version and level, scope of claim, evaluation method, and date of evaluation.

2. Where should a conformance claim be published?

On the accessibility statement page, linked from the site footer, and included in procurement documentation.

3. Why is the evaluation method important to include?

It demonstrates that the claim is based on actual testing rather than assumptions.

4. How often should a conformance claim be updated?

At least annually or after significant changes that affect accessibility.

5. Challenge: Write a conformance claim for your own website or a site you manage. Include all four required components.

FAQ

Mini Project

Create a complete conformance claim page for a fictional product or for your own project. Include WCAG version, level, scope, evaluation method, date, exceptions, and contact information.

What's Next

Learn about Conformance Requirements including how conformance is verified and maintained. Then explore WCAG-EM the evaluation methodology.