Shift-left accessibility: Embedding inclusion early in agile projects

Agile has redefined the way we develop software by emphasising the importance of early feedback, iterative progress and adapting to change. However, accessibility, often represented by the portmanteau 'a11y' (with the 'A' as the first letter, followed by 11 characters and ending with 'Y'), is frequently an afterthought, only being addressed during final testing or post-release fixes. This approach increases the cost of change and excludes users with disabilities during the most critical phases of product development. The solution is shift-left accessibility, which is similar to shift-left quality and shift-left security.

In Agile and DevOps, the shift-left principle involves moving code integration, testing, and quality assurance earlier in the development process. The shift-left principle is also applied to quality, known as shift-left quality. In this approach, quality begins at the requirements-gathering stage, where well-defined User Stories are written. It then continues through coding, where test-driven development is employed, and extends to code reviews, where peer reviews focus on code quality, before the testing phase. Quality analysts are engaged from the earliest stages of product development. Similarly, in shift-left security, application security begins right from the design phase and continues through coding and review rather than being an afterthought.  When applied to accessibility, this means integrating inclusive design considerations from the outset of the project, during the ideation process, customer journey mapping, User Story creation, Product Backlog Refinement and Sprint Planning, with a view to ensuring accessibility-compliant coding.
Rather than viewing accessibility as a final checklist, shift-left integrates it into the way teams ideate, plan and deliver software. This transforms accessibility from a compliance burden into a competitive advantage.

According to the World Health Organization, over 1 billion people — nearly 15% of the global population — live with some form of disability. Not only is ignoring accessibility ethically questionable, it is also economically inefficient. Accessible design enhances creativity, broadens market reach, improves usability and reduces legal risks. 
Furthermore, designing for accessibility sparks innovation as well as inclusion. Microsoft’s Xbox Adaptive Controller has redefined inclusive gaming. Apple’s VoiceOver and AssistiveTouch have transformed device interaction for users with disabilities and anyone seeking hands-free or simplified controls. Similarly, Google's Live Transcribe and Live Caption services, which were initially developed for deaf and hard of hearing people, are now being used in virtual meetings, noisy environments and multilingual situations. Similarly, Microsoft’s Immersive Reader, initially designed to support users with dyslexia or reading difficulties, is now embraced by educators and professionals alike for its ability to improve comprehension and focus. Even YouTube’s auto-captioning, once a niche accessibility tool, has become an expected feature of online content. These examples demonstrate that accessible design fosters inclusive and intuitive digital experiences while providing a competitive advantage and tangible business value.
By integrating accessibility from the outset, teams can create products that benefit everyone, including those facing temporary or situational limitations.

1. Include accessibility in the Definition of Done (DoD)

Ensure that accessibility is part of the acceptance criteria for every User Story. This will keep it at the forefront of everyone's minds throughout the sprint lifecycle.

2. Design with inclusion in mind

Include personas for users with situational, temporary or permanent disabilities. Ensure that the UI/UX design incorporates accessible colour contrasts, keyboard navigability and screen reader support. Involve accessibility experts or users with disabilities in usability testing.

3. Train the team

Agile relies on cross-functional teams. Training developers, testers and designers in WCAG (Web Content Accessibility Guidelines) guidelines and accessibility testing tools can dramatically reduce defects in the post-production stage. Training Product Owners on the importance of inclusive designs and universal products ensures that accessibility features are incorporated into User Stories and acceptance criteria.

4. Automate early

Integrate accessibility linting tools and automated tests into CI/CD pipelines. Tools such as Axe-Core, Pa11y and Lighthouse can identify common issues before the code is deployed.

5. Backlog Refinement

Include accessibility in Backlog Refinement. Evaluate stories for inclusivity, refining them to include accessibility requirements where applicable.

6. Review accessibility debt

Just as we review technical debt, we should also review 'accessibility debt'. Retrospectives can help teams reflect on how well they incorporated inclusive practices during a sprint.

• Faster iteration: Identifying accessibility issues at an early stage reduces the need for rework, and using automated tools such as axe-core accelerates delivery.
• Broader user base: Inclusive products attract and retain a more diverse user base, providing a competitive edge.
• Stronger team culture: Embedding accessibility encourages empathy and shared responsibility among designers, Product Owners, Developers, and validation engineers.
• Regulatory readiness: Using automated tools helps Developers comply with recognized accessibility standards such as the Web Content Accessibility Guidelines (WCAG), the Americans with Disabilities Act (ADA) in the US and EN 301 549, the European accessibility standard for ICT (information and communication technology) products and services. Meeting these standards not only improves agility but also reduces the risk of legal issues.

Shift-left accessibility is not about creating more work, but about changing our mindset. When Agile teams prioritise inclusion at the start of the development phase, they achieve compliance goals and create better, more robust products.
Treating accessibility as a core element of project quality and user experience aligns the team with the Agile principles of customer focus, technical excellence and delivering sustainable solutions that work for everyone.