Through the integration of automation into its software development lifecycle, Slack has improved accessibility testing, guaranteeing a more inclusive user experience for those with impairments. Slack’s continued dedication to accessibility is seen in the effort, which complies with the Web Content Accessibility Guidelines (WCAG).
About Slack
Slack is a well-known platform for collaboration that unifies people, projects, and apps in one workplace. Channels for structured communication, project management tools, and smooth connection with more than 2,600 programs, such as Office 365 and Google Drive, are among its features. AI capabilities are also incorporated into Slack to improve workflows and productivity.
Automating Accessibility Compliance
Slack has traditionally worked with outside testers while adhering to internal accessibility guidelines. Although manual testing is still crucial for detecting some subtle problems, the business realized that automated testing was required to actively find accessibility violations.
Slack chose Axe, a popular tool known for its WCAG compliance, to incorporate automatic accessibility checks into its development workflow in 2022. The effort was hampered by conflicts that arose while integrating Axe into pre-existing test frameworks, especially with the React Testing Library (RTL) and Jest.
The accessibility team at Slack investigated Playwright, a testing framework that works with Axe through the @axe-core/playwright package, in order to address these problems. The team took a calculated approach in spite of early difficulties while incorporating Axe checks into Playwright’s Locator object. After important user activities, accessibility checks were introduced to make sure the material was fully rendered before assessment.
By focusing on major violations and removing rules that weren’t relevant, Slack adjusted its Axe implementation. With the integration of the checks into Playwright’s fixture model and a new function called runAxeAndSaveViolations, developers may now start checks within test specs. This arrangement enhanced accessibility validation while maintaining efficiency.
Improving the reporting was another important objective. Slack provided screenshots and violation information using Playwright’s HTML Reporter to raise awareness of accessibility concerns. Custom error messages were added to test results to help make them easier to interpret.
Slack grouped its accessibility tests into a non-blocking test suite that copied crucial functionality tests in order to reduce duplication. These Tests can be run locally by developers, scheduled for repeating runs, or incorporated into continuous integration (CI) pipelines. A dedicated Jira workflow that facilitates tracking and prioritizing accessibility violations ensures collaboration between the accessibility team and developers.
By balancing automated and manual testing, Slack aims to offer a scalable, efficient, and inclusive approach to accessibility validation. The company’s ongoing investment in automation shows how committed it is to providing a faultless user experience for all.