Google

Disabled people use Google's accessibility features (Live Caption, TalkBack, Lookout, Project Relate) to navigate digital life on the platforms billions depend on, while absorbing the labor when the same company's reCAPTCHA blocks them, auto-captions fail them, and platform updates break the workflows they cannot opt out of.

ENABLE Model location

• Builder-side Interventions → Set Requirements that Include Accessibility
• Builder-side Interventions → Create Accessible Content
• Builder-side Interventions → Design Accessible Experiences
• Builder-side Interventions → Develop Accessible Implementations
• Builder-side Interventions → Test for Accessibility
• Builder-side Interventions → Iterate to Address Shortcomings
• Navigator-side Compensations → Use Assistive Technologies
• Navigator-side Compensations → Create Workarounds
• Navigator-side Compensations → Submit Feedback to Creators
• Navigator-side Compensations → Switch to an Alternative
• navigator-side/endure-inaccessibility

What it is

Google develops and maintains Chrome (approximately 66% global browser market share), Android (72%+ global mobile market share, reaching 95% in India and 85% in Africa), YouTube (over 2 billion logged-in users monthly), Google Workspace (used by over 9 million organizations), and reCAPTCHA (deployed on millions of websites worldwide).^{1 2} When Google builds accessibly, billions of people benefit. When it doesn't, disabled people in schools, governments, and workplaces that mandated Google tools must compensate. In the Global South, where Android is often the only operating system available, there is no alternative.

Google's Central Accessibility Team, led by Eve Andersson since 2013, builds features like Live Caption (real-time captions for any audio), TalkBack (Android's built-in screen reader), Lookout (object and text recognition for blind users), Live Transcribe (speech-to-text for deaf and hard of hearing people), and Project Relate (a research app that uses personalized AI models trained on over one million speech samples to recognize atypical speech caused by conditions like ALS, cerebral palsy, and stroke).^{3 4} Laura Allen, Google's Director of Accessibility and Disability Inclusion, brings lived experience to the team. She has choroidal osteomas, a rare condition that destroyed her central vision. She lost sight in her left eye at age 10 and her right eye at 14. Allen joined Google in a sales role in 2010 and spent 6.5 years as Senior Accessibility Program Manager for Chrome and ChromeOS before moving into her current strategy role.^{5 6}

Google is also a corporate sponsor of NV Access, the nonprofit that builds NVDA, the free, open-source screen reader used by 65.6% of screen reader users worldwide.⁷ This is builder-side investment in assistive technology infrastructure: a corporation funding the tool that compensates for inaccessible web content, including Google's own.

Google also builds reCAPTCHA, the most significant accessibility barrier on the web. The 2024 WebAIM Screen Reader User Survey found that CAPTCHAs scored 2,172 on the problematic items index, nearly 75% higher than the second-ranked barrier (interactive elements, at 1,239).⁷ The W3C's own analysis concluded that "traditional CAPTCHAs effectively make a site inaccessible to blind users" and that audio alternatives are inaccessible to deaf users. Deafblind users cannot complete either challenge.⁸ reCAPTCHA is a Google product, deployed across millions of websites, and it is the single largest barrier that screen reader users encounter online.

YouTube auto-captions, launched in 2009, extended access to video content for deaf and hard of hearing viewers, but the accuracy gap made them unreliable. Deaf YouTuber Rikki Poynter launched the #NoMoreCRAPtions campaign in 2016 to document the problem: auto-generated captions so inaccurate that videos about concealers produced captions about zebras.^{9 10} YouTube also offered a community captions feature that allowed volunteers to contribute captions to videos. The feature provided access that auto-captions could not, but it also shifted builder-side content labor to unpaid volunteers. It was abused by trolls who inserted offensive or misleading text. In 2020, YouTube removed community captions, citing low usage and spam. A Change.org petition protesting the removal collected over 40,000 signatures. Poynter responded: "While I do acknowledge and have called out the fact that the feature gets abused by trolls, I know that the feature brings accessibility that we didn't have before to the table."¹¹ The ENABLE Model identifies community captions as an accessibility ultimatum: YouTube built the tool, volunteers produced the access. The question is whether the builder-side tools that remained (auto-captions, creator caption editing in YouTube Studio, SRT uploads) were adequate to make that navigator-side labor unnecessary.

Why it matters

Google illustrates how the same organization can simultaneously deliver genuine builder-side care and impose navigator-side burden at scale.

Google's scale amplifies both care and neglect. Chrome holds approximately 66% of global browser market share. Android runs on 72%+ of the world's mobile devices. YouTube hosts more video content than any platform in history. When Google ships an accessibility improvement, such as Live Caption expanding to seven languages or Expressive Captions conveying tone and environmental cues, millions of disabled people benefit overnight.¹² When Google ships a regression, such as Chrome breaking NVDA math rendering or Workspace stripping PDF tags, millions of disabled people lose access overnight. There might not be another company whose accessibility decisions propagate so far so fast.

ReCAPTCHA is a builder-side barrier. Google builds accessibility features to reduce navigator-side burden. Google also builds reCAPTCHA, which the WebAIM survey identifies as the single most problematic barrier screen reader users face, by a 75% margin over the next-ranked item.⁷ The W3C has documented that visual CAPTCHAs are inaccessible to blind users and audio CAPTCHAs are inaccessible to deaf users, meaning deafblind users cannot complete either challenge.⁸ reCAPTCHA is a Google product, actively maintained by Google, deployed across millions of websites, and it blocks the people Google's accessibility team is simultaneously trying to serve.

TalkBack reigns over the Global South. Android holds 95% mobile market share in India and 85% in Africa.² In these regions, TalkBack is not one screen reader option among several. It is the only screen reader most blind users will likely have. Yet accessibility researchers at netz-barrierefrei.de assessed that "VoiceOver is ahead of TalkBack by at least four years, and Google has no discernible interest in catching up."¹³ The researchers documented persistent issues: large speech output delays, an extremely error-prone keyboard, and integration so poor that TalkBack "feels like an external screen reader, thrown together and not fully integrated."¹³ For the billion-plus people in regions where Android is the default, TalkBack's quality determines whether blind people can use a phone at all. Apple's VoiceOver is more polished, but Apple's phones cost four to ten times more. The global south's reliance on TalkBack becomes a structural expression of precarity.

YouTube built a community captions tool. Volunteers produced the captions. YouTube got accessible content without doing the captioning itself. The ENABLE Model names this pattern an accessibility ultimatum: the builder builds the infrastructure, the navigator does the work. The feature was abused by trolls, and removing it was defensible if the builder-side replacement was ready. But Poynter's #NoMoreCRAPtions campaign had spent four years documenting that auto-captions were not ready. The captions were so inaccurate they constituted misinformation, not access.⁹ The question is not whether YouTube should have kept community captions forever. Shifting captioning labor from navigators to builders is the right direction. The question is whether YouTube retired the navigator-side tool before the builder-side content was adequate. Auto-caption accuracy has improved significantly since 2020, but the gap between removal and adequacy was borne by the deaf users who lost the only reliable captions many videos had.¹¹

Schools, governments, and employers mandate Google Workspace through institutional procurement, concentrating platform dependence in ways that limit user exit. When Google iterates (expanding Live Caption languages, improving TalkBack gestures), millions benefit. When Workspace products lag, disabled people who cannot opt out must compensate. Until December 2024, Google Docs exported PDFs without accessibility tags, producing documents that screen readers could not read from the productivity suite that schools and governments required their users to use.¹⁴ The University of Colorado's accessibility office advised screen reader users to avoid Google Sites entirely and noted that Google Drive's own interface did not fully support screen readers.¹⁵ When the product is mandatory and the product is inaccessible, the labor of access falls entirely on the user.

Screen reader users report fearing updates because regressions arrive without warning. A Chromebook user posted: "I'm afraid of updating my Chromebook due to updates causing changes/severe bugs to screen reader."¹⁶ In December 2024, a Chrome update broke math rendering for NVDA users. Perkins School for the Blind advised users to switch to Firefox as a workaround, noting that "Google's accessibility team has been notified of the issue, but no timeline was provided for a fix."¹⁷ When accessibility features regress without acknowledgment or timeline for repair, this constitutes abandonment. Access that once existed becomes unreliable.

Real-world examples

In the news

How Designing For Disabled People Is Giving Google An Edge (2016)
-- Mark Sullivan, Fast Company

• Eve Andersson described Google's accessibility philosophy: "the accessibility problems of today can lead to the technology breakthroughs of tomorrow." Features like voice typing and autocomplete became mainstream after originating as accessibility tools. This builder-side approach treats accessibility as innovation, not compliance. The article's frame ("giving Google an edge") reveals whose benefit drives the narrative.³

YouTube Axes Community Captions Feature, Citing Low Usage (July 2020)
-- Liam O'Dell

• YouTube removed its community captions feature, a navigator-side tool that shifted captioning labor to volunteers but was also abused by trolls. Deaf journalist Liam O'Dell documented the backlash: a Change.org petition collected over 40,000 signatures, and Deaf YouTuber Rikki Poynter (who had spent four years campaigning against inaccurate auto-captions through #NoMoreCRAPtions) noted the feature "brings accessibility that we didn't have before to the table." The tension is an ENABLE Model question: retiring a navigator-side compensation is the right move when builder-side content is ready to replace it. Whether auto-captions and creator tools were ready in 2020 is what the Deaf community disputed.¹¹

Resolved issue with Google Chrome, NVDA and math (December 2024)
-- Perkins School for the Blind

• A Chrome update broke math rendering for NVDA users. Perkins advised users to switch to Firefox, noting "Google's accessibility team has been notified of the issue, but no timeline was provided for a fix." When platform updates break accessibility, users must compensate by switching to alternatives while waiting for fixes that may or may not come.¹⁷

Google Update - Vision Related Accessibility Enhancements from Q3 2024 (October 2024)
-- American Foundation for the Blind AccessWorld

• Google's Q3 2024 updates added AI-powered OCR to ChromeOS Select-to-Speak, "enabling text-to-speech for inaccessible or scanned PDFs directly in the Chrome PDF viewer." The AFB also documented five new help center articles for Workspace screen reader users, showing active iteration and accessibility documentation maintenance.¹⁸

• Laura Allen described what drew her to accessibility work at Google: after joining in a sales role, she "quickly noticed ways that products she used every day, like Docs and Gmail, could be improved for blind or low-vision users like herself." Her path from noticing gaps as a disabled user to leading the strategy that addresses them illustrates the difference between external advocacy and embedded authority.⁵
• Vision Australia identified multiple WCAG 2.1 Level AA failures in embedded Google Maps: rating stars not announced to screen readers, illogical keyboard focus order, and the satellite view button entirely missing from the focus order. Vision Australia met with Google Maps' Product Lead to present the findings. No timeline for fixes was provided.¹⁹
• Google Docs exported PDFs without accessibility tags until December 2024. Every PDF produced by Google Docs for the preceding decade-plus was inaccessible to screen readers by default. The fix, when it arrived, produced what one accessibility researcher described as "a not-horrible option" for basic documents.¹⁴
• Project Relate uses personalized AI models trained on over one million speech samples to recognize atypical speech caused by ALS, cerebral palsy, Down syndrome, Parkinson's disease, stroke, and traumatic brain injury. The app transcribes speech to text, restates it in synthesized voice, and translates voice commands for Google Assistant.⁴ As of 2026, the app is not accepting new users.
• University IT departments document that "due to the accessibility issues that exist with Google Sites, it is recommended that web developers who utilize a screen reader use other web publishing services." For Google Drive, the University of Colorado notes that "the combination of JAWS for Windows and Firefox may be used but may not provide full support within the Google Drive interface."¹⁵

What care sounds like (builder-side interventions)

Care at Google involves treating accessibility as a requirement, not a feature request:

• "The accessibility problems of today can lead to the technology breakthroughs of tomorrow." -- Eve Andersson³
• "Block the release until the screen reader flow works end to end."
• "We're expanding Live Caption to seven more languages so deaf people worldwide can participate."
• "We test every Chrome release against NVDA, JAWS, and VoiceOver before shipping."
• "We fund NV Access because the screen reader our users depend on shouldn't cost $1,475 a year."

What neglect sounds like (builder-side interventions)

Neglect involves shipping products without accessibility verification, or building barriers while simultaneously claiming to remove them:

• "Ship now and fix accessibility later." *1
• "That regression affects too few users to block the launch." *2
• "We recommend users switch to Firefox as a workaround." *3
• "Due to the accessibility issues that exist with Google Sites, it is recommended that web developers who utilize a screen reader use other web publishing services."¹⁵ *4

*1: By "later," Google Docs exported untagged PDFs for over a decade before adding accessibility tags in December 2024.
*2: Screen reader users number 250,000+ on NVDA alone. A regression in Chrome affects more blind people than live in most cities.
*3: The recommendation came from Perkins School for the Blind, not from Google, because Google provided no workaround of its own.¹⁷
*4: Google's own documentation acknowledging that its own product is inaccessible, while the same company builds accessibility features for other products.

What compensation sounds like (navigator-side compensations)

Compensation describes the labor disabled people carry when Google's accessibility iteration lags, regresses, or contradicts itself:

• "I'm afraid of updating my Chromebook due to updates causing changes/severe bugs to screen reader."¹⁶
• "I spin up a Windows virtual machine just to finish assignments everyone else completes natively in Google Docs."
• "For now, consider using the Firefox web browser as an alternative." (the workaround blind users must adopt when Chrome breaks)¹⁷
• "To make a doc accessible for most people, it is best to convert a Google Doc to a Microsoft Word document."¹⁵
• "The CAPTCHA won't let me through. I can't see the images and the audio is garbled. I need someone to log in for me."
• "The auto-captions said 'zebras' when the video was about concealers. I gave up trying to follow."

---

All observations occur within the context of the global commercial technology platform ecosystem, where Google's accessibility decisions (both care and neglect) propagate to billions of users across products that schools, governments, and employers mandate, and where disabled people in the Global South depend on Google's Android and TalkBack as their only path to digital participation.

Footnotes

1. StatCounter: Browser Market Share Worldwide ↩

2. StatCounter: Mobile Operating System Market Share ↩ ↩²

3. Fast Company: How Designing For Disabled People Is Giving Google An Edge ↩ ↩² ↩³

4. Google Research: Project Relate ↩ ↩²

5. Be My Eyes: Laura Allen, For This Accessibility Leader, Finding an Inclusive Workplace Changed Everything ↩ ↩²

6. Blind Abilities: How a Journey Through Vision Loss Prepared Laura Allen ↩

7. WebAIM: Screen Reader User Survey #10 ↩ ↩² ↩³

8. W3C: Inaccessibility of CAPTCHA ↩ ↩²

9. 3Play Media: Faces Behind the Screen, Rikki Poynter ↩ ↩²

10. Wikipedia: Rikki Poynter ↩

11. Liam O'Dell: YouTube Axes Community Captions Feature, Citing Low Usage ↩ ↩² ↩³

12. Google Blog: Android accessibility update, expanded dark theme, Gemini in TalkBack ↩

13. netz-barrierefrei.de: Android TalkBack, An Alternative to VoiceOver for the Blind? ↩ ↩²

14. Eclecticism: Google Docs Adds PDF Accessibility Tagging ↩ ↩²

15. University of Colorado OIT: Google Workspace Accessibility, Drive ↩ ↩² ↩³ ↩⁴

16. Chromebook Community: Fear of updating due to screen reader bugs ↩ ↩²

17. Perkins School for the Blind: Resolved issue with Google Chrome, NVDA and math ↩ ↩² ↩³ ↩⁴

18. AFB AccessWorld: Google Update, Vision Related Accessibility Enhancements from Q3 2024 ↩

19. Vision Australia: Embedded YouTube and Google Maps, are they accessible? ↩