WCAG 5.3.1: Required elements of the conformity declaration

Understanding WCAG Conformance Declarations

While not a direct Success Criterion that content must meet, the requirement for specific elements within a WCAG conformance declaration is fundamental to establishing trust and transparency in an organization’s accessibility efforts. This documentation outlines the essential components mandated by the Web Content Accessibility Guidelines (WCAG) 2.0 and 2.1 for any valid claim of conformance. A well-formed conformance declaration serves as a public statement attesting to a website’s or application’s adherence to WCAG standards, specifying the version, level, and scope of compliance.

Why a Conformance Declaration Matters

A transparent and accurate conformance declaration is crucial for several reasons:

• Building Trust: It demonstrates an organization’s commitment to accessibility and provides a verifiable statement of their efforts, fostering trust with users, partners, and regulators.
• Legal and Regulatory Compliance: Many laws and policies globally (e.g., ADA, Section 508, EN 301 549) reference WCAG as a standard. A clear conformance claim is often a prerequisite for demonstrating legal compliance and can be critical in avoiding legal challenges.
• Facilitating Procurement: Organizations procuring digital products and services can use conformance claims to evaluate potential vendors’ accessibility maturity and ensure purchased solutions meet required standards.
• Guiding Users and Developers: It offers clarity on the expected accessibility experience, helping users understand what to expect and providing a reference for developers on the target accessibility level.
• Transparency and Accountability: It holds organizations accountable for their accessibility statements and encourages ongoing maintenance and improvement.

WCAG Conformance Claim Requirements

The WCAG 2.0 and WCAG 2.1 guidelines specify five core requirements that must be met to make a valid claim of conformance. These are detailed in Section 5, “Conformance Claims (Optional)” of the WCAG specification. While making a claim is optional, if one is made, it must include the following elements:

• 1. Date of Claim: The date on which the conformance claim was made. This is important for understanding the currency of the claim.
• 2. Guidelines Title, Version, and URI: The full title of the guidelines, including the version number, and the URI to that version. For example: “Web Content Accessibility Guidelines 2.1 at https://www.w3.org/TR/WCAG21/”.
• 3. Conformance Level: The specific conformance level achieved (A, AA, or AAA). This must be clearly stated.
• 4. Scope of the Claim: A clear, unambiguous description of the web pages, parts of pages, or applications to which the claim applies. This could be an entire website, a specific section, or a single web application.
• 5. List of Supported Technologies (Optional but Recommended): A list of the web content technologies relied upon to meet the guidelines. Technologies are considered “relied upon” if the content would not conform if that technology were turned off or not supported. Examples include HTML, CSS, client-side scripting (JavaScript), ARIA, etc. While optional, providing this enhances clarity.

Practical Guidelines for Compliance

To ensure your conformance declaration is accurate and useful, consider these practical steps:

• Dedicated Accessibility Statement Page: Create a specific page on your website for your accessibility statement. This page should be easily discoverable, typically linked from the website’s footer.
• Regular Audits: Conduct thorough and regular accessibility audits of your content to verify your conformance level before making or updating a claim.
• Clear and Concise Language: Write your statement in plain language that is easy for both technical and non-technical audiences to understand.
• Maintain and Update: Accessibility is an ongoing process. Ensure your conformance claim is reviewed and updated whenever significant changes are made to your website or application, or when new accessibility issues are discovered and resolved.
• Provide Contact Information: Include details on how users can provide feedback or report accessibility issues. This shows commitment and provides a channel for continuous improvement.

Examples

Correct Implementation

A well-structured accessibility statement clearly articulates all required elements.

Incorrect Implementation

An incomplete or vague statement fails to meet the WCAG requirements for a valid claim.

This incorrect example lacks the date, the full title and URI of the WCAG version, a specific scope, and important contextual information. Such a statement offers little verifiable information and does not meet the requirements for a formal WCAG conformance claim.

Best Practices and Common Pitfalls

Best Practices:

• Detailed Scope: Clearly define the boundaries of your claim. Specify exact URLs, sections, or applications covered. If only a portion of a site conforms, state which portions do not.
• Living Document: Treat your accessibility statement as a living document. Establish a review schedule to ensure it remains accurate and up-to-date.
• User Feedback Mechanism: Actively solicit and respond to user feedback regarding accessibility. This demonstrates commitment and provides valuable insights.
• Include an Exclusion Statement (if applicable): If certain parts of your content do not conform, document these clearly with reasons and planned remediation efforts.
• Reference Testing Methodologies: Briefly mention how accessibility was tested (e.g., manual testing, automated tools, user testing) to add credibility.

Common Pitfalls:

• Missing Required Elements: Failing to include the date, full WCAG title/URI, conformance level, or clear scope.
• Vague Scope Definition: Using generic terms like “our website” without specifying the exact pages, sections, or domains covered.
• Outdated Information: Not updating the claim when the website undergoes significant changes, leading to inaccurate representations of current accessibility.
• Claiming Conformance Without Verification: Stating conformance without thorough and regular accessibility audits. This can lead to legal exposure and reputational damage.
• Not Addressing Third-Party Content: Failing to account for the accessibility of embedded third-party content (e.g., videos, widgets) within the scope of the claim. If you rely on third-party content, clarify your approach to its accessibility.