What is shift left testing and how does it relate to accessibility?

Shift left testing is a software development philosophy that prioritizes testing as early as possible in the development process. For example, instead of relying on a dedicated testing phase right before launch, testing is integrated throughout the entire project lifecycle. This helps catch bugs sooner, which makes them easier and cheaper to fix.

The shift left concept is super useful for accessibility testing as well. Fixing accessibility issues at the end of development can become a bottleneck. It’s better to implement feedback loops in the planning, design, and development phases that account for accessibility best practices.

Here are some ways to apply shift left testing for accessibility:

• Plan for it from the start – Consider detailing accessibility requirements as part of the initial project scope. This will help the project team understand that building an accessible website is a key part of project success.
• Designer and developer collaboration – Get developers involved in the design review to foster a shared focus for accessibility best practices. This also gives teams an opportunity to discuss implementation concerns before development begins.
• Developer feedback – Include accessibility testing in code reviews so developers can hold each other accountable for writing accessible code. The frequency of code reviews varies by project, but avoid having only one review and the end of the development.
• Automated build process tools – Integrate accessibility testing tools (like Axe, Lighthouse, or Pa11y) into the development pipeline. These automated tools can’t test for everything related to accessibility, but they can help catch issues early.

By thinking about accessibility early and often, we make websites that are more inclusive and avoid costly rework late in the process.