Expand my Community achievements bar.

Integrate Accessibility Testing into AEM Cloud Manager Pipeline

Avatar

Employee

11/7/24

Request for Feature Enhancement (RFE) Summary:

We propose adding accessibility testing to the AEM Cloud Service Cloud Manager pipeline, providing a baseline assurance for compliance with the European Accessibility Act (EAA) and the Web Content Accessibility Guidelines (WCAG) 2.x.

 

By embedding accessibility checks directly into the CI/CD process, this feature would enable proactive identification and resolution of accessibility issues, fostering a more inclusive user experience and aligning with industry standards.

Use-case:
  • Compliance with Accessibility Standards (EAA, WCAG 2.x):
    Ensuring compliance with the European Accessibility Act (EAA) and WCAG 2.x is critical for organizations operating in Europe or serving global audiences. Automated testing within the Cloud Manager pipeline would provide a baseline for meeting these legal standards, reducing the risk of non-compliance and associated penalties.

  • Early Detection of Accessibility Issues:
    By running accessibility checks at each deployment, teams can catch issues as they arise in the development lifecycle rather than after the website has gone live. This proactive approach enables timely fixes, reducing the effort and cost of retrofitting accessibility after deployment.

  • Consistent Accessibility Checks Across Updates:
    Websites evolve over time with new content, features, and design updates. Automated testing ensures that accessibility remains a consistent focus, regardless of these changes. Testing at each deployment helps maintain high accessibility standards without relying solely on manual checks.

  • Enhanced User Experience for All Audiences:
    Regular accessibility checks improve the overall user experience, particularly for users with disabilities. By identifying and resolving barriers to access, organizations can create a more inclusive experience that caters to all users, increasing engagement and satisfaction.

  • Real-Time Visibility into Accessibility Status:
    Integrating accessibility testing into Cloud Manager provides real-time feedback for each deployment, helping teams monitor the site's accessibility status over time. This visibility allows for better tracking of improvements, trends, and issues, fostering a culture of accessibility awareness.

  • Reduced Dependence on External Tools and Manual Processes:
    Teams often use separate tools or manual processes for accessibility testing, which can lead to inconsistencies and require additional setup. Having accessibility testing directly within AEM Cloud Manager centralizes this process, reducing dependency on external resources and making it easier to manage compliance in a unified way.

  • Quick, Actionable Reporting for Developers:
    Axe DevTools CLI provides actionable insights into specific accessibility issues, helping developers understand and fix problems more efficiently. Integrating this into Cloud Manager would give development teams immediate feedback on violations, with clear paths to resolution, accelerating the remediation process.

  • Simplified Audits and Documentation:
    Regular automated testing creates a log of accessibility compliance that can be used for audits, internal reviews, or reporting to regulatory bodies. With consistent testing and reporting, organizations can better document their commitment to accessibility and provide proof of compliance if needed.

  • Improved Cross-Functional Collaboration:
    Accessibility compliance often involves collaboration across teams, including developers, designers, and content authors. With a centralized testing system in Cloud Manager, different stakeholders have easy access to results and can work together to address issues, fostering a more collaborative and inclusive approach to accessibility.

  • Optimized Resource Allocation for Accessibility Work:
    Automated testing helps teams identify which pages and components are non-compliant, allowing them to allocate resources more effectively. For example, developers can prioritize fixes on the highest-traffic pages, ensuring that accessibility efforts are strategically focused on areas with the most impact.

  • Simplified Enablement of Accessible Design Practices:
    Regularly surfacing accessibility issues through automated testing encourages teams to design and develop with accessibility in mind from the start. Over time, this helps build a team culture that prioritizes accessibility, reducing the frequency of issues in future releases.

  • Risk Mitigation in High-Visibility or High-Risk Deployments:
    For major releases or updates to high-traffic pages, automated accessibility testing provides an extra layer of assurance that all users will have a positive experience. This is especially important for key marketing pages or campaign launches, where accessibility oversights could negatively impact a large audience.

  • Simplified Accessibility Compliance for Multiple Geographies:
    Many organizations operate in multiple regions, each with different accessibility standards. Automated testing within Cloud Manager can help ensure compliance across various legal frameworks by testing for standards like WCAG 2.x, reducing the risk of non-compliance regardless of location.

Current/Experienced Behavior:

Adobe Experience Manager (AEM) Cloud Service currently does not include built-in accessibility testing as part of its Cloud Manager pipeline.

Accessibility compliance checks are often handled through external tools or manual processes, resulting in potential inconsistencies and increased risk of non-compliance with standards like WCAG 2.x and EAA requirements.

This can make it challenging to maintain consistent accessibility standards across updates.

Improved/Expected Behavior:

We recommend integrating automated accessibility testing within the AEM Cloud Manager pipeline. This enhancement could use a solution like Axe DevTools CLI to conduct accessibility tests on either a set of pre-configured pages or the customer’s 20 most-visited HTML pages, provided the site is not headless. This would give developers a reliable way to identify accessibility issues within the CI/CD process, ensuring regular compliance checks and addressing issues early in the development lifecycle.

 

Key benefits would include:

  • Consistent accessibility testing aligned with WCAG 2.x and EAA standards.
  • Proactive issue identification within the CI/CD pipeline.
  • Enhanced usability for all users through improved accessibility compliance.
Environment Details (AEM version/service pack, any other specifics if applicable):  
Customer-name/Organization name: e.g. VodafoneZiggo
Screenshot (if applicable):  
Code package (if applicable):  
1 Comment

Avatar

Administrator

11/20/24

@rwunsch-adobe 

Thanks for proposing this idea.
This has been reported to the engineering under the internal reference SITES-27062. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.
Status changed to: Investigating