Shift left: what does it mean?

The concept of "shifting left" has emerged as a game-changer in the world of web development, particularly in the realm of web accessibility. As the demand for digital inclusivity grows, it's essential to understand what "shift left" means and how it's transforming the way we approach web accessibility.

Defining "Shift Left"

"Shift left" is a philosophy that advocates for integrating accessibility into web development from the earliest stages. Imagine the stages of web development lined up in a row, with the beginning stages at the left and the latter ones on the right. Just as the term suggests, "shift left" is about moving the focus and application of accessibility practices to an earlier phase in the development process.

A flow chart of job roles. From left to right is listed BA, design, dev then testing, with an arrow pointing right from one to the next

Traditionally, accessibility concerns have been addressed later in the development lifecycle like during testing or even after a project's completion through user feedback. This often leads to reactive fixes, increased costs, and missed opportunities to create an inclusive user experience. "Shift left" in web accessibility, however, flips this approach on its head: it urges developers, designers, business analysts and stakeholders to embrace accessibility as a fundamental aspect of every stage of the development journey.

The Pillars of "Shift Left" in Web Accessibility:

  1. Early Consideration: "Shift left" emphasises integrating accessibility considerations during the ideation and planning phases of a project. This ensures that accessibility isn't an afterthought but a core consideration from the outset.

  2. Design and Prototyping: Create user interfaces that inherently prioritise accessibility. Elements like colour contrast, navigation, and content structure are designed with inclusivity in mind. Acceptance criteria outline requirements for accessibility.

  3. Development and Coding: Accessibility principles are woven into the coding process itself by adhering to semantic HTML and using ARIA sparingly.

  4. Testing: Use automated testing tools like website scanners early in development to help identify accessibility issues promptly, allowing for immediate remediation. When work makes it to the testing phase of development, only minor bugs should be found.

"Websites developed with a shift left approach are more likely to provide a seamless experience for all users, regardless of their abilities."

Benefits of "Shift Left" in Web Accessibility:

Incorporating accessibility into your workflow provides significant business advantages, and doing it in a shift left approach is the most time- and cost-effective way to do so.

These benefits include:

  • Cost-Efficiency: Fixing accessibility issues early in the process is more cost-effective than retroactively addressing them post-launch.

  • Inclusive User Experience: Websites developed with a "shift left" approach are more likely to provide a seamless experience for all users, regardless of their abilities.

  • Positive Brand Image: Prioritising accessibility demonstrates a commitment to inclusivity, enhancing your brand's reputation and attracting a wider audience.

  • Mitigating Legal Risk: In an era of increasing accessibility lawsuits, "shift left" reduces the risk of legal challenges by ensuring compliance from the start.

Check out this article about the business case for web accessibility for more reasons to adopt shift left.

Conclusion

"Shift left" in web accessibility is a transformative paradigm that emphasises integrating accessibility practices and testing into every phase of web development. By making accessibility a foundational element rather than an add-on, we create a digital landscape that embraces diversity and empowers users of all abilities. As we navigate the ever-evolving digital frontier, "shift left" guides us towards a more inclusive, equitable, and user-centric online world.

"Shift left in web accessibility flips this approach on its head: it urges developers, designers, business analysts and stakeholders to embrace accessibility as a fundamental aspect of every stage of the development journey."


Find out more about Aleph Accessibility's auditing, training and consulting services. Or get in touch to start or accelerate your accessibility journey.

Previous
Previous

Accessibility Checklist for mobile content

Next
Next

Accessibility Checklist for animated content