The concept of “shift-left” in the context of accessibility refers to the practice of integrating accessibility considerations early and regularly in the product development lifecycle, rather than addressing them at the end of the process.

This approach aims to identify and resolve accessibility issues as early as possible, which can lead to more inclusive and user-friendly products, as well as cost savings and improved efficiency.

Examples of shift-left accessibility

Planning phase

• Define accessibility goals and requirements.
• Include accessibility criteria in documentation.
• Allow time in the development phase for accessibility requirements.

Design phase

• Consider how keyboard navigation will flow through your designs and how users will interact with the interactive elements.
• Use accessible design principles and patterns.
• Conduct usability testing with a diverse range of users.

Coding/development phase

• Implement semantic HTML and WAI-ARIA attributes.
• Perform code reviews with a focus on accessibility.

Testing phase

• Use inspection tools to check for common accessibility issues.
• Conduct manual testing with assistive technologies.
• Test functionality with the keyboard.

Release phase

• Ensure all user-facing content is accessible.
• Monitor and gather feedback from users to inform updates.

By adopting a shift-left approach to accessibility, we can create more inclusive and user-friendly products and improve accessibility throughout the development lifecycle.