Accessibility Testing Just Got More Smarter: Explore New Features for A11Y Testing

1. Merge Accessibility Reports: Simplify Your Workflow

Managing multiple accessibility reports for different accessibility tests has always been a cumbersome task. Now, with our Merge Accessibility Reports feature, you can easily combine multiple accessibility reports into a unified, single report. Whether you’re testing two or more URLs, simply select the reports, choose bulk actions, name your combined report, and hit save. No more redundancy, view all your accessibility findings in one place.

Key Benefits of Merge Accessibility Reports:

• Users can effortlessly merge two accessibility reports into a single consolidated report with a simple manual selection, making it easier to compare results and save time during the analysis phase.
• Automatically removes duplicate accessibility issues for URLs that appear in both reports, ensuring that only unique issues are presented. This eliminates the clutter of redundant data and offers a clearer picture of your website’s accessibility status.
• Upon initiating the merge, users are prompted to give the new report a name, which defaults to “Merged Report – Date, Time,” ensuring easy identification. The report will also display the username of the person who initiated the merge, enhancing accountability and tracking.

2. Passed Test Cases: Full Transparency with WCAG Compliance

As accessibility testers, we know how important it is to track both violations and successes. The Show Passed Cases in Web feature brings full transparency to your reports by displaying accessibility checks that pass WCAG compliance alongside violations. This feature works for both manual and automated testing, helping you highlight the areas where your application is doing well, essential for regression testing, compliance reporting, and providing feedback to developers. Enable this feature and gain better insight into the accessibility requirements your application already meets.

Key Benefits of Show Passed Cases in Web:

• Complete view of your accessibility status, fostering greater visibility into your app’s compliance progress.
• Track and compare the results of previously passing accessibility tests to identify potential regressions, ensuring that code changes don’t inadvertently break existing accessibility standards.
• Generate comprehensive reports that demonstrate both achievements and areas for improvement, helping you effectively communicate progress to stakeholders and facilitate audits.

Note: Check out the documentation for the Passed Test Cases feature .

3. Capture Screenshot Capability in Accessibility: Visual Context for Better Debugging

Sometimes, words aren’t enough to describe an issue, visuals speak louder. With the Capture Screenshot Capability in both manual and automated testing, you can now automatically capture annotated screenshots that highlight the exact location of accessibility violations. Screenshots include red bounding boxes that visually map out the problem areas, offering instant visual context to developers. This feature makes debugging more efficient and documentation more comprehensive.

Key Benefits of Capture Screenshot Capability:

• Automatically captures full-page screenshots with visual annotations, allowing testers to easily pinpoint the location of issues on any part of the page, including those hidden from view.
• By eliminating the need for manual screenshots and visual inspections, the feature significantly reduces the time spent troubleshooting accessibility issues, making your testing process faster and more efficient.
• Available across all supported testing frameworks, the screenshot capture capability ensures consistency and ease of use, whether you’re conducting manual or automated tests.

Note: Check out the documentation for Capture Screenshot Capability feature .

4. Fragment Identifiers: Enhanced Precision in Accessibility Audits

For those of us working with single-page applications (SPAs) or complex web pages with fragment identifiers (the portion after the # symbol in URLs), the Fragment Identifiers feature is a game-changer. By enabling this feature, you can treat URLs with different fragment identifiers as separate entities, offering more precise tracking of accessibility issues. This ensures you can categorize and resolve issues on specific sections of a page, rather than grouping them all under a single URL. It enhances the audit process for SPAs, improves workflow efficiency, and enables detailed reporting for each section of the page.

Key Benefits of Fragment Identifiers:

• Enables precise categorization of accessibility issues based on specific sections of a page, providing clearer insights into where improvements are needed within a complex URL.
• Allows better tracking of accessibility issues in SPAs that use hash-based routing, ensuring accurate reporting and management of issues across different page states.
• Facilitates detailed, section-specific reports that empower teams to prioritize fixes and track progress on individual page segments, leading to more efficient issue resolution.

Note: Check out the documentation for the Fragment Identifiers feature .