WCAG 5.2.1: Conformance Level

Introduction: Understanding WCAG Conformance Levels

The Web Content Accessibility Guidelines (WCAG) provide a globally recognized standard for making web content more accessible to people with disabilities. A critical aspect of applying WCAG is understanding and declaring your level of conformance. This criterion, while not a specific technical requirement for content creation, defines how an organization communicates the extent to which their web content meets WCAG standards.

A WCAG conformance claim indicates the achievement of accessibility targets for a given web page or set of web pages. It is a formal statement detailing which version of WCAG (e.g., WCAG 2.1) and which conformance level (A, AA, or AAA) has been met.

What is WCAG Conformance?

Conformance in the context of WCAG refers to meeting all the success criteria for a specific level. It means that the web content has been designed and developed in a way that aligns with the guidelines and provides a certain baseline of accessibility for users with various disabilities. Declaring a conformance level is a way for organizations to demonstrate their commitment to accessibility and provide transparency to their users.

The Three Levels of Conformance (A, AA, AAA)

WCAG defines three levels of conformance, each building upon the previous one, representing increasing degrees of accessibility:

• Level A (Minimum): This is the lowest level of conformance. It addresses the most fundamental and critical accessibility barriers. Content conforming to Level A removes significant obstacles, allowing many users with disabilities to access the information. Achieving Level A is a baseline, often considered legally essential in many jurisdictions.
• Level AA (Recommended): This is the most commonly targeted and recommended level of conformance for most websites and applications. Level AA builds upon Level A by addressing a broader range of accessibility issues, including many common and significant barriers for users with disabilities. Achieving Level AA typically provides a good user experience for the majority of users with disabilities.
• Level AAA (Optimized): This is the highest and most comprehensive level of conformance. It aims to provide the best possible accessibility for the widest range of users with disabilities. Achieving Level AAA for all content can be very challenging and may not be feasible for all types of content or organizations, as some success criteria at this level may conflict with the design or functionality requirements of certain types of content.

It is important to note that if content meets Level AA, it inherently also meets Level A. Similarly, if content meets Level AAA, it meets both Level A and Level AA.

Why Conformance Level Matters

Declaring a WCAG conformance level is more than just a technical formality; it has significant implications for various stakeholders:

• Legal Compliance: Many countries and regions, such as the United States (ADA), European Union (EN 301 549), and Canada, have laws and regulations that mandate specific WCAG conformance levels (most commonly AA) for public-facing websites and digital services. A clear conformance claim helps demonstrate compliance.
• User Trust and Experience: A public conformance statement signals to users with disabilities that an organization cares about their access needs. It builds trust and assures them that efforts have been made to create an inclusive experience. Users can then make informed decisions about whether they can effectively use a particular website or service.
• Organizational Accountability: For organizations, declaring a conformance level fosters internal accountability. It provides a measurable goal for development teams and content creators, encouraging them to integrate accessibility throughout the design and development lifecycle.
• Market Reach: Accessible websites reach a broader audience, including people with disabilities, older adults, and individuals using mobile devices or in challenging environmental conditions (e.g., bright sunlight). This expands potential customer bases and improves market penetration.

WCAG Requirements for a Conformance Claim

For a WCAG conformance claim to be valid, it must meet five specific requirements outlined in the WCAG guidelines (Section 5. WCAG Conformance).

1. Full Pages

   Conformance applies to full Web pages only. This means that all content on the page, including embedded content, must conform or a conforming alternative version of the page must be provided. You cannot claim conformance for only a portion of a page.

2. Complete Processes

   If a Web page is part of a series of Web pages that presents a complete process (e.g., a multi-step registration form or an e-commerce checkout), then all pages in the process must conform at the specified level, or a conforming alternative must be provided for the entire process.

3. Only WCAG-Relied-Upon Technologies

   Only accessibility-supported ways of using technologies can be relied upon to satisfy the success criteria. This means that if a technology is used, it must be supported by users’ assistive technologies and web browsers. Technologies that are not accessibility-supported cannot be relied upon for meeting conformance.

4. Non-Interference

   Any technologies that are not accessibility-supported or that are used in a non-accessibility-supported way must not interfere with the user’s ability to access the rest of the page. This means that if non-conforming elements exist, they must not prevent a user from accessing the conforming content.

5. Accessibility-Supported Ways of Using Technologies

   All technologies used to deliver the content must be used in an “accessibility-supported” way. This implies that the technology works with users’ assistive technologies (e.g., screen readers, magnifiers) and accessibility features of browsers. Developers should use well-established and commonly used technologies and techniques.

Additionally, a conformance claim should generally include:

• The date of the claim.
• The guidelines title, version, and URI (e.g., WCAG 2.1 at https://www.w3.org/TR/WCAG21/).
• The conformance level met (A, AA, or AAA).
• A clear description of the Web content to which the claim applies (e.g., a specific URI, a list of URIs, or a description of the scope).
• The list of Web technologies that the content relies upon (e.g., HTML, CSS, JavaScript, ARIA).

Practical Guidelines for Compliance (Making a Conformance Claim)

Choosing the Right Conformance Level

The choice of conformance level depends on several factors:

• Legal Requirements: Check local and national accessibility laws. Most mandate WCAG 2.1 Level AA.
• Target Audience: Consider the diverse needs of your users. Level AA generally serves a wide audience effectively.
• Content Type and Complexity: Some content, like live video or complex interactive tools, might make Level AAA difficult or impossible to achieve for certain criteria.
• Resources and Budget: Achieving higher levels requires more effort, time, and potentially specialized expertise.

For most organizations, WCAG 2.1 Level AA is the recommended and pragmatic target, balancing strong accessibility with achievable implementation.

Crafting an Accessibility Statement

An accessibility statement is the ideal place to publish your conformance claim. This statement should be easily discoverable on your website, often linked from the footer.

<h3>Accessibility Statement</h3>
<p>This accessibility statement applies to [Your Website Name/URL], owned by [Your Organization].</p>
<p>We are committed to making our website accessible to all users, regardless of ability. We are continually improving the user experience for everyone and applying the relevant accessibility standards.</p>
<p>We aim to conform to <strong>WCAG 2.1 Level AA</strong>. Our most recent accessibility audit was conducted on <strong>[Date of Audit, e.g., October 26, 2023]</strong>. This statement applies to all pages and content under the primary domain <strong>[Your Domain Name, e.g., example.com]</strong>.</p>
<p>The technologies relied upon for conformance include <strong>HTML5, CSS3, JavaScript, and WAI-ARIA</strong>.</p>
<p>We welcome your feedback on the accessibility of our website. Please let us know if you encounter accessibility barriers: <a href="mailto:accessibility@example.com">accessibility@example.com</a>.</p>

<h3>Accessibility Note</h3>
<p>Our website tries to be accessible. We think most people can use it.</p>
<p>We use HTML.</p>

Best Practices and Common Pitfalls

Best Practices

• Regular Auditing: Accessibility is an ongoing process. Conduct regular audits and user testing (including people with disabilities) to ensure sustained conformance.
• Integrated Accessibility: Embed accessibility into your design and development workflows from the start, rather than treating it as an afterthought.
• Clear Communication: Provide a prominent and detailed accessibility statement that is easy to find and understand.
• Document Exceptions: If certain parts of your site cannot meet the desired conformance level (e.g., third-party widgets), document these exceptions and provide alternative ways for users to access the information.
• Stay Updated: WCAG guidelines evolve. Stay informed about new versions (e.g., WCAG 2.2, WCAG 3.0) and emerging best practices.

Common Pitfalls

• Claiming Without Verification: Making a conformance claim without thorough testing and validation against the WCAG success criteria is a significant pitfall, potentially leading to legal issues and reputational damage.
• Static Claims: Content changes frequently. A conformance claim made once and never updated quickly becomes inaccurate. Ensure your claim reflects the current state of your website.
• Misunderstanding “Accessibility-Supported”: Relying on technologies or techniques that are not widely supported by assistive technologies or browsers can invalidate a conformance claim.
• Partial Conformance Misrepresentation: Claiming conformance for an entire website when only a few pages or sections have been tested, or when critical parts of a process are inaccessible, is misleading. Remember the “Full Pages” and “Complete Processes” requirements.
• Aiming Too High (AAA) Without Justification: While aspirational, aiming for AAA for an entire complex site can be unrealistic and lead to frustration or failure. It’s often better to reliably achieve AA than to incompletely aim for AAA.

Conclusion

Understanding and correctly applying WCAG conformance levels is fundamental to building an accessible and inclusive web presence. By carefully evaluating your content against the WCAG success criteria and making a clear, accurate conformance claim, you demonstrate a commitment to accessibility that benefits all users and helps meet legal and ethical obligations. Remember that accessibility is a continuous journey, and maintaining your chosen conformance level requires ongoing effort and vigilance.