WCAG 5.3.2: Optional Components of a Conformance Claim
Introduction
Web Content Accessibility Guidelines (WCAG) conformance claims are formal statements by an organization or individual declaring that a specific web page or set of web pages adheres to WCAG standards at a particular level. While WCAG defines specific required components for such claims, Conformance Requirement 5.3.2 addresses the inclusion of optional components.
This criterion highlights that a conformance claim may include additional information beyond the minimum requirements. While not mandatory for achieving a valid claim, incorporating these optional details can significantly enhance the clarity, credibility, and usefulness of the accessibility statement for users and stakeholders alike.
What is a Conformance Claim?
A conformance claim is a public declaration of a website’s or web content’s accessibility status. It serves as a concise summary of the efforts made to ensure accessibility, specifying the WCAG version and conformance level achieved (A, AA, or AAA), and the scope of content covered.
The primary purpose of a conformance claim is to provide transparency and build trust with users, particularly those with disabilities, by clearly stating the accessibility features and limitations of the content.
Understanding Optional Components
Conformance Requirement 5.3.2 allows for flexibility in presenting a conformance claim. Beyond the essential information needed to make a claim valid, organizations can choose to include supplementary details that provide deeper context, explain the methodologies used, or offer additional resources. This optional information serves to enrich the claim, making it more informative and helpful without burdening the claimant with mandatory additional work.
Why Optional Components Matter
While not strictly required for a claim to be valid, including optional components offers significant advantages for both users and the organizations making the claim.
Benefits for Users
- Enhanced Trust and Transparency: Detailed information about testing, technologies, and accessibility features builds confidence in the claim’s authenticity.
- Better Informed Decisions: Users, especially those relying on specific assistive technologies, can better understand if a website is likely to work well with their setup. For example, knowing which screen readers were used for testing can be highly valuable.
- Improved User Experience: Providing contact information for feedback or detailing future accessibility plans can make users feel heard and valued, fostering a more inclusive digital environment.
Benefits for Organizations
- Demonstrates Commitment: Going beyond the minimum required shows a proactive and thorough commitment to accessibility, differentiating an organization from those who only meet the bare minimum.
- Proactive Communication: Addressing common questions or concerns upfront can reduce support inquiries related to accessibility.
- Internal Accountability: Documenting testing processes, specific technologies, and ongoing efforts can reinforce internal accessibility practices and encourage continuous improvement.
- Risk Mitigation: A comprehensive accessibility statement that includes detailed optional information can provide a stronger defense against potential legal challenges by demonstrating due diligence.
WCAG Conformance Requirements
To fully understand Conformance Requirement 5.3.2, it’s important to first review the mandatory components of a conformance claim as outlined in WCAG 2.0 and 2.1.
Required Components of a Conformance Claim (WCAG 2.0 & 2.1, Conformance Requirement 5.3.1)
According to WCAG, a valid conformance claim must include the following five pieces of information:
- Date: The date on which the claim was made.
- Guidelines Title, Version & URI: The title, version, and Uniform Resource Identifier (URI) of the guidelines to which the content conforms (e.g., WCAG 2.1,
https://www.w3.org/TR/WCAG21/
). - Conformance Level: The conformance level achieved (A, AA, or AAA).
- Scope: A comprehensive list of the web pages to which the claim applies, or a URI for content that lists the pages, along with a description of how the pages were selected.
- Technologies Relied Upon: The list of Web technologies that the content relies upon.
WCAG 2.0 Conformance Requirement 5.3.2: Optional Components of a Conformance Claim
This specific requirement states: “A conformance claim may also include optional information.”
This means that beyond the five mandatory components, organizations have the flexibility to add any other relevant details that they believe enhance the clarity, transparency, or comprehensiveness of their accessibility statement.
Practical Guidelines for Including Optional Information
When deciding to include optional components, consider what information would be most valuable to your users and best represent your organization’s accessibility efforts.
Types of Optional Information
- Specific Technologies Used: Detail specific versions of HTML, CSS, JavaScript frameworks, or content management systems (CMS) that are part of the content.
- Testing Methodology: Describe how the content was tested, including:
- Automated testing tools used (e.g., Axe, Lighthouse).
- Manual testing processes.
- User testing with individuals with disabilities.
- Expert accessibility audits.
- Assistive Technologies (AT) and User Agents Tested: List the specific browsers (with versions), operating systems, and assistive technologies (e.g., JAWS, NVDA, VoiceOver, ZoomText) used during testing.
- Accessibility Contact Information: Provide an email address, phone number, or feedback form for users to report accessibility issues or ask questions.
- Exclusions or Limitations: Clearly state any known issues, non-conforming parts of the content, or specific areas that are under development.
- Future Accessibility Plans: Outline upcoming accessibility improvements or a roadmap for reaching higher conformance levels.
- Date of Last Review/Update: Indicate when the accessibility statement was last reviewed or updated.
- Organizational Commitment Statement: A brief statement outlining the organization’s dedication to digital accessibility.
Best Practices
- Keep it Relevant and Accurate: Ensure all optional information is truthful, current, and directly pertains to the accessibility of the content.
- Be Concise but Comprehensive: Provide enough detail to be informative without overwhelming the reader. Consider linking to a more detailed accessibility statement or policy if information is extensive.
- Structure for Readability: Use headings, lists, and clear paragraphs to make the information easy to scan and understand.
- Maintain Distinctness: Clearly separate optional information from the required components to avoid confusion.
Common Pitfalls
- Information Overload: Including excessive, irrelevant details can make the claim hard to navigate and diminish its impact.
- Outdated Information: Optional details, especially regarding technologies or testing, can quickly become obsolete. Ensure regular reviews and updates.
- Using Optional Info to Obscure Issues: Never use optional components to distract from or hide non-conformance with required success criteria.
- Confusing Optional with Required: Misunderstanding what is optional versus what is mandatory can lead to an invalid conformance claim, even if a lot of extra information is provided.
Examples
The following examples illustrate how optional components can be effectively integrated into an accessibility statement. Note that a full conformance claim would typically be more extensive and might reside on a dedicated accessibility page.
Correct Implementation Example (Claim with Optional Components)
This example demonstrates a valid conformance claim that includes both required and several optional components, enhancing transparency and detail.
Accessibility Conformance Statement
- Date: 2023-10-27
- Guidelines: Web Content Accessibility Guidelines (WCAG) 2.1
- URI: https://www.w3.org/TR/WCAG21/
- Conformance Level: AA
- Scope: All pages within the ‘
/products/
‘ and ‘/services/
‘ sections of example.com, including the homepage (https://www.example.com
). These pages represent the core user flows and were sampled systematically. - Technologies Relied Upon: HTML5, CSS3, JavaScript (ECMAScript 2018)
- (Optional) Specific Technologies Used: React v18, SASS, Node.js (for server-side rendering).
- (Optional) Testing Methodology:
- Automated testing using Axe-core (latest version) integrated into CI/CD pipeline.
- Manual testing performed by certified accessibility specialists using keyboard navigation, screen reader checks (NVDA on Windows, VoiceOver on macOS), and color contrast analyzers.
- User testing with 5 individuals with various disabilities (low vision, motor impairment, cognitive disability) conducted in Q3 2023.
- (Optional) Assistive Technologies & User Agents Tested:
- Browsers: Chrome (v118), Firefox (v118), Safari (v17)
- Screen Readers: NVDA (v2023.2), JAWS (v2023), VoiceOver (macOS Sonoma)
- Operating Systems: Windows 11, macOS Sonoma
- (Optional) Accessibility Contact: For feedback or issues, please email accessibility@example.com or call +1-800-555-0199.
- (Optional) Future Plans: We are committed to achieving WCAG 2.1 AAA conformance for our documentation section by Q2 2024.
- (Optional) Last Reviewed: 2023-10-25
Incorrect Implementation Example (Invalid Claim Despite Optional Components)
This example demonstrates a claim that fails to meet the WCAG conformance requirements for required components, even though it includes optional information. The optional components cannot compensate for missing mandatory details.
Accessibility Statement
- Date: October 27, 2023
- Guidelines: WCAG 2.1
- Conformance Level: AA
- Technologies Relied Upon: HTML, CSS, JavaScript
- (Optional) Testing Performed: Automated scans using various tools.
- (Optional) Contact: info@example.org
- (Optional) Our Commitment: We strive for an accessible web experience for all users.
Reason for incorrectness: This claim is invalid because it fails to provide two crucial required components from WCAG 5.3.1:
- Missing URI for Guidelines: Only “WCAG 2.1” is stated, but the official URI (e.g.,
https://www.w3.org/TR/WCAG21/
) is omitted. - Missing Scope: There is no clear list of the web pages to which the claim applies, or a URI for content that lists the pages. Without a defined scope, the claim is meaningless.
The presence of optional information like ‘Testing Performed’ or ‘Contact’ does not make up for the absence of these mandatory elements. A conformance claim must first satisfy all required components to be considered valid.
Conclusion
Conformance Requirement 5.3.2 highlights the flexibility and value of enriching a WCAG conformance claim with optional information. While the core five components are essential for a valid claim, judiciously adding details about technologies, testing, and organizational commitment can transform a basic statement into a powerful tool for transparency and trust. By providing this additional context, organizations not only demonstrate a deeper commitment to accessibility but also empower users with the information they need to navigate the digital world effectively. Always remember that optional components supplement, but never replace, the critical required elements of a conformance claim.