The 11 Steps in my A11y Journey


Thursday 15th,

2:30 p.m. – 3:15 p.m.


Talks (Track 2) – Indoor Hall

Session Type

25-minute Talk,

All levels


Tester, Developer, Team Lead


  • Have the resources to propose accessibility work in your own team
  • Know how to advocate for people who might not be your users.....yet
  • Be able to explain the importance of building accessibility into your products

Building accessibility in can seem daunting. However, breaking the task down into small pieces of work can help everyone see the value and the results.

Have you ever wondered how accessible the application you're working on is? Do you know how to find out how (in)accessible it is? Where do you even start with getting buy-in from your team to fix it? Where do you start fixing it once you have that buy-in? I asked myself all of these questions when I started my new job. I joined a new team and I was eager to jump into accessibility work. I knew our mobile app was not accessible. I knew we needed to fix it but the task seemed massive. I had no buy-in from my team. People didn’t think we needed to do the work because they’d had no complaints from users about accessibility. I had to win the team around and build a justification for investigating the work. I built my case on the legislation we needed to comply with and high-profile court cases to demonstrate the risk if we didn’t. Once I had buy-in from the team, we worked together to explore how we could possibly approach the problem. We looked at how people interacted with our application. We identified key user journeys through our application. We broke those user journeys down into the screens and actions involved to take a journey from start to finish. Finally, we prioritised those journeys based on business impact. Together, let’s explore the 11 steps I took with my team to building accessibility in within 3 months. We'll look at * How to frame the proposal to your team to do the work * Ways to break the approach down into manageable sized pieces of work that deliver value at every step * Why we chose the user journeys we worked on