Category: WCAG Principles and Conformance

Full Conformance

Also known as: Fully Conformant

Simply put

Full conformance means a piece of digital content or technology satisfies all of the requirements set out in an applicable standard, rather than only some of them. In the context of WCAG, a version of a web page that is fully conformant meets every applicable success criterion for the chosen conformance level. Meeting a standard's requirements is not the same as guaranteeing an accessible experience for every user or ensuring legal compliance, and this entry is not legal advice.

Formal definition

Full conformance refers to satisfying all criteria stated in a specification's conformance clause, which is the section that enumerates the requirements that must be met to claim conformance (NIST). Under WCAG 2.2, the W3C notes that a page can offer multiple versions of content, and at least one version must be fully conformant to satisfy the applicable conformance requirement; a fully conformant version meets all relevant success criteria at the selected level (A, AA, or AAA) along with the other conformance requirements. This concept should be distinguished from Section 508 usage, where 'conformance' means providing information and communication technology (ICT) that meets the applicable parts of the ICT Final Standards and Guidelines, and where conformance is treated separately from broader 'compliance.' Because conformance addresses whether stated technical requirements are met, it does not by itself establish usability for all users or immunity from legal claims, and automated testing alone can verify only a subset of requirements; manual and assistive technology testing are generally required.

Why it matters

Full conformance is the benchmark that turns a vague commitment to accessibility into a testable claim. When an organization states that a web page is fully conformant to a standard such as WCAG at a chosen level, it is asserting that every applicable requirement for that level has been satisfied, not merely a subset. This distinction matters because partial conformance can leave significant barriers in place while still allowing an organization to point to accessibility work it has done. Understanding what full conformance actually requires helps teams set accurate expectations internally and avoid overstating their accessibility posture in public statements, accessibility conformance reports, or vendor documentation.

Who it's relevant to

Accessibility Engineers and QA Testers

Engineers and testers responsible for evaluating digital content need to know that full conformance means satisfying every applicable success criterion at the chosen level, not just the ones detectable by automated tools. Because automated testing verifies only a subset of requirements, manual review and assistive technology testing are generally necessary to substantiate a full conformance claim.

Compliance Officers

Compliance officers should distinguish conformance from compliance, particularly in Section 508 contexts where the two terms are treated separately. Establishing that ICT conforms to applicable standards addresses stated technical requirements, but it is a distinct question from whether an organization satisfies its broader legal and policy obligations.

Product and UX Teams

Product owners and designers benefit from understanding that meeting a standard's requirements does not by itself guarantee a usable experience for every user. Full conformance is a measurable target, but teams should pair it with usability evaluation involving people who use assistive technologies to identify barriers that success criteria alone may not capture.

Legal Counsel and Business Leaders

Counsel and leadership should recognize that a full conformance claim is a technical assertion, not a guarantee of immunity from legal claims. Because accessibility requirements evolve through regulation and case law, decisions about legal exposure should rely on current authorities and qualified legal advice rather than on a conformance claim alone.

Procurement Teams and Vendors

Teams evaluating third-party products and vendors making accessibility representations need a shared understanding of what full conformance entails, including which standard and conformance level are being claimed and how that claim was verified. This helps ensure that conformance statements in accessibility documentation reflect the full set of applicable requirements rather than a partial evaluation.

Inside Full Conformance

Conformance to a Full Web Page

Under WCAG, conformance is claimed for full web pages only; partial conformance for portions of a page is not permitted. A conformance claim covers the entire page as delivered to the user.

Complete Processes

When a page is one of a series of pages presenting a process (such as a multi-step checkout or form submission), all pages in that process must conform at the specified level for full conformance to be claimed for any page in the process.

Specified Conformance Level

Full conformance is stated at a chosen level: A, AA, or AAA. Meeting a level requires satisfying all success criteria at that level and all lower levels. AA is the level most commonly cited as a target in policies and settlements.

Satisfying All Applicable Success Criteria

Full conformance requires that every applicable success criterion at the claimed level is met, with no exceptions carved out, subject to WCAG's own conformance requirements.

Accessibility-Supported Technologies

Conformance relies on ways of using technologies that are supported by users' assistive technologies and browsers. Techniques used to satisfy criteria must be accessibility-supported to count toward conformance.

Non-Interference

Technologies that are not relied upon for conformance must not block a user's ability to access the rest of the page, so that content remains usable even when some technologies are turned off or unsupported.

Common questions

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

Does achieving full WCAG conformance guarantee that my site is legally compliant with the ADA?

No. Full conformance describes meeting a defined set of WCAG success criteria at a chosen level, but it is not the same as legal compliance. The ADA is a US civil rights law and does not itself contain codified web technical specifications; courts and settlements have often referenced WCAG as a benchmark rather than as a fixed legal rule. Meeting conformance criteria may reduce risk and support an accessibility case, but it does not guarantee immunity from legal claims. Requirements continue to evolve through regulation and case law, and you should consult qualified legal counsel for advice specific to your situation.

If my content fully conforms to WCAG, does that mean it is fully usable and accessible for everyone?

Not necessarily. Conformance and real-world usability are distinct. Meeting the applicable success criteria does not guarantee an accessible experience for all users with all disabilities and assistive technologies. Automated testing detects only a portion of potential issues, so manual review and testing with assistive technology are generally needed. Full conformance is a meaningful baseline, but usability testing with people who use assistive technologies often surfaces problems that formal conformance does not capture.

What conformance level should we target for full conformance?

Level AA is the level most commonly cited as a target, and it is frequently referenced in settlements, agency guidance, and organizational policies. Full conformance at a given level generally means satisfying all applicable success criteria at that level (and the levels below it). Some organizations pursue selected AAA criteria where feasible, though AAA is generally not expected across all content. The appropriate target may depend on the authority that applies to you, such as Section 508 for covered federal contexts or Title II or Title III of the ADA.

Which WCAG version should we conform to?

This depends on what applies to your context and the standards referenced in any applicable policy, regulation, or agency guidance. WCAG 2.0, 2.1, and 2.2 differ, with later versions adding success criteria; conforming to a newer version generally includes the earlier version's requirements. Because criteria differ across versions and levels, it is important to state the specific version and level you are claiming. Confirm the current expectations for your jurisdiction, and where a federal context applies, check the standard referenced by the relevant authority.

How do we verify that we have achieved full conformance?

Verification generally combines multiple methods. Automated tools can efficiently flag certain issues but detect only a portion of them, so manual evaluation and testing with assistive technologies are typically required to assess the remaining criteria. A full conformance claim is generally supported by documenting the scope of content evaluated, the version and level targeted, and the testing methods used. Re-evaluation is commonly needed as content changes over time.

Can we claim full conformance for our entire website?

A conformance claim generally applies to a defined scope, such as specific pages, a set of pages, or complete processes, rather than being an open-ended claim about an entire evolving site. Third-party content, dynamic content, and frequently updated material can complicate maintaining conformance across all pages. It is generally advisable to clearly state the scope covered, the version and level, and the date of evaluation, and to note that conformance can change as content is added or modified.

Common misconceptions

Full conformance can be claimed for just the accessible parts of a page while excluding problematic sections.

WCAG does not allow partial conformance claims for portions of a page. A conformance claim applies to the entire page, and where a page is part of a process, all pages in that process must also conform.

Achieving full WCAG conformance guarantees legal compliance and immunity from accessibility claims.

Conformance to a technical standard is distinct from legal compliance. In the US, obligations arise under laws such as the ADA, Section 508, and Section 504, and courts and settlements have often referenced WCAG as a benchmark rather than a codified rule. Conformance does not by itself guarantee protection from claims; consult qualified legal counsel.

If a page passes automated accessibility testing, it has achieved full conformance.

Automated tools detect only a portion of possible issues. Full conformance requires satisfying all applicable success criteria, which generally demands manual review and testing with assistive technologies, and meeting criteria does not guarantee a usable experience for all users.

Best practices

Define the target conformance level explicitly (commonly WCAG 2.1 or 2.2 Level AA) and confirm the specific version and level with your policy or legal counsel before making a claim.

Evaluate conformance at the level of full pages and complete processes, ensuring every page in a multi-step flow meets the claimed level rather than testing pages in isolation.

Combine automated testing with manual review and assistive technology testing, since automated checks alone cannot confirm full conformance.

Verify that the techniques used are accessibility-supported by the browsers and assistive technologies your users rely on, and document those assumptions.

Check that technologies not relied upon for conformance do not interfere with access to the rest of the page when unsupported or disabled.

Treat any conformance claim as a snapshot subject to change, re-evaluate as content and standards evolve, and consult qualified legal counsel regarding how conformance relates to applicable legal obligations.