Google: Building accessibility through innovation, partnership and continuous learning
Insights shared by Christopher Patnoe, EMEA Accessibility and Disability Inclusion Lead for Google, gathered by our EDI Manager, Daisy March.
"Only someone in the community can tell you what’s broken. And then they can tell you how they hack it to make it work for them. Our job as technologists is to take that hack and make it broadly applicable."
Christopher Patnoe
Google develops products and services used by billions of people around the world every day, from Android and Chrome to Search, YouTube, Workspace and Pixel devices. With technology playing such a significant role in modern life, accessibility is a critical part of ensuring that everyone can participate fully in the digital world.
When I spoke to Christopher Patnoe, Google’s EMEA Accessibility and Disability Inclusion Lead, he was refreshingly honest about the realities of accessibility in such a large organisation. Despite Google’s reputation as a leader in the field, Christopher was quick to point out that accessibility is not something an organisation ever fully “solves”. Instead, it is a continual process of listening, learning and improving.
At Google, accessibility is thoroughly embedded throughout the product development process. Dedicated accessibility specialists work alongside product teams, while disabled employees and external users are involved in everything from early-stage concept development and co-design sessions through to user testing and product refinement. For more complex or innovative products, disabled users are often brought in at the earliest stages to help shape solutions before development begins.
Google regularly works with external communities, gathers feedback from disabled users and provides dedicated support channels for customers with disabilities. This creates a feedback loop that allows products to evolve as people’s needs and expectations change.
Something that I was particularly impressed by during our conversation was the extent to which accessibility innovation is driven by lived experience. Christopher shared several examples of products that originated from disabled employees and their families. One of these was Live Transcribe, a speech-to-text application that began life during a Google hackathon, led by Dmitri, a deaf software engineer.
Another was Guided Frame, a Pixel feature that helps blind and low-vision users take photographs independently, notifying users when the subject matter is within frame. The idea originated from a Google employee whose blind son wanted to take skateboard selfies in the same way as his friends. Through ongoing collaboration with disabled users, the technology has continued to evolve and improve over time.
These examples demonstrate a wider principle at Google: accessibility is not viewed as a niche requirement but as a source of innovation and inspiration – it’s about always asking “what’s next?”.
Christopher also highlighted how many accessibility features ultimately benefit a much broader audience. Live Caption on the Chrome Browser and Android Operating System, for example, was originally developed to support deaf and hard-of-hearing users, but it is now used by people in noisy environments, language learners and neurodivergent users too.
Google also invests heavily in building accessibility knowledge internally. New employees working in product-related roles are introduced to accessibility concepts early on, while more specialised training is delivered through the internal Alphabet Accessibility Academy. The Academy provides role-specific learning pathways for engineers, researchers, designers, product managers and other professionals, helping teams understand how accessibility relates directly to their work.
Alongside formal training, Google runs annual events such as Accessibility and Disability Innovation Week, creating opportunities for employees around the world to learn more about disability, accessibility and inclusive design. Christopher noted that one of the challenges is keeping accessibility visible enough to remain a priority, without overwhelming people with information.
Rather than focusing solely on compliance metrics or usage statistics, Google recognises the importance of individual stories and lived experiences. In a company whose products reach billions of users, even a seemingly small improvement can have a meaningful impact on millions of people. At the same time, he acknowledged that raising awareness remains one of the greatest challenges, requiring constant communication and engagement across a large and diverse organisation.
Reflecting on Google’s approach, three key lessons emerged:
Design with disabled people, not for them
Involving people with lived experience throughout the design process leads to more meaningful, effective and innovative solutions.
View accessibility as a driver of innovation rather than a compliance exercise
Many of the most impactful technologies arise from solving barriers experienced by disabled users and often go on to benefit a much wider audience.
Accept that accessibility is never finished
User needs evolve, technology changes and new barriers emerge. Successful organisations treat accessibility as an ongoing process of improvement rather than a one-off project.
It was refreshing to learn that even a leader in innovation like Google doesn’t feel it has all the answers. However, they recognise the value of including diverse perspectives in all stages of product development, and the importance of putting human experience at the heart of innovation.