7 March 2026 — PageLive Project
Summary
This report documents the difficulties a screen reader user encounters when using Gemini. Testing was conducted using NVDA on Chrome on a Windows desktop. While the findings are based on NVDA, the barriers described are expected to affect users of other screen readers, including JAWS, in similar ways. While Gemini is usable with a screen reader, several interactions require significant extra effort or guesswork that sighted users do not face.
1. Scope and Testing Environment
This analysis evaluates the screen reader experience on Gemini as encountered during manual testing. The scope is limited to interactions that are part of routine use: composing and reading conversations, navigating between chats, and accessing application controls.
Findings are not evaluated against WCAG criteria. The focus is on the practical experience of a screen reader user during everyday tasks.
| Screen Reader | NVDA 2025.3.3.54605 |
| Browser | Chrome 145.0.7632.117 |
| Platform | Windows Desktop |
| Interface Tested | gemini.google.com web application |
Findings are classified by their impact on task completion:
- Blocker — The task cannot be completed.
- Barrier — The task can be completed, but requires significant additional effort, guesswork, or repeated keystrokes that are not required of sighted users.
- Friction — The task works as expected, but the experience is degraded in a way that compounds over extended use.
2. Findings
2.1 Response Completion Is Not Announced
Severity: Barrier
When Gemini finishes generating a response, no announcement is made to the screen reader. The response content is not placed in a live region, so the screen reader does not notify the user that new content is available or that generation has completed.
As a result, the user has no reliable way to know when it is appropriate to begin reading. The user must manually navigate to the chat area, attempt to locate the new response, and determine through repeated keystrokes whether generation has finished or is still in progress. This interaction occurs on every single exchange, making it the most consequential barrier in routine use.
2.2 Formulas and Symbols Are Not Read by the Screen Reader
Severity: Blocker
When a Gemini response contains mathematical formulas or symbolic notation, the screen reader does not read these elements. They are invisible in the accessibility tree, meaning the user receives no indication that content is present at those positions in the response.
A user relying on a screen reader cannot access any part of a response that contains formulas or symbols. For conversations involving mathematics, science, or other notation-heavy topics, this renders significant portions of Gemini's output completely inaccessible.
2.3 Dialog Appearance Is Not Announced
Severity: Barrier
When dialogs open within Gemini, the screen reader does not announce their appearance and focus is not moved into them. The user receives no indication that anything has changed on screen and must discover through navigation that a dialog has appeared.
2.4 No Means of Reviewing Chat Flow and Navigation Within Long Conversations
Severity: Barrier
Gemini does not provide a structured means for a screen reader user to review the flow of a conversation or navigate directly to a specific prompt or response within a long chat. The user must traverse the entire chat history sequentially to locate a previous exchange, with no mechanism to jump to a known position.
For sighted users, the visual layout of the conversation provides immediate orientation. For screen reader users, long conversations require a proportionally greater traversal effort with no compensating navigational aid.
2.5 Missing Keyboard Shortcuts for Frequently Used Actions
Severity: Friction
The following actions do not have keyboard shortcuts in Gemini:
- Jump to the chat input field
- Start a new chat
- Delete the current chat
- Announce the last response
Each of these actions is available through the interface but requires the user to locate the relevant control through navigation. For a sighted user, these controls are immediately visible. For a screen reader user, the location of a button is not always remembered between sessions, and finding it requires traversal through surrounding content.
The absence of shortcuts does not prevent these actions. However, the cumulative effect of repeated traversal meaningfully degrades the experience of extended use.
3. Summary of Findings
| # | Finding | Severity |
|---|---|---|
| 2.1 | Response completion not announced | Barrier |
| 2.2 | Formulas and symbols not read by screen reader | Blocker |
| 2.3 | Dialog appearance not announced | Barrier |
| 2.4 | No means of reviewing chat flow in long conversations | Barrier |
| 2.5 | Missing keyboard shortcuts for common actions | Friction |
4. Further Reading
This article is part of the PageLive project's documentation for Gemini. A companion article, Screen Reader Experience Mitigation on Gemini, describes how PageLive addresses the barriers identified above. For a full list of keyboard shortcuts and features PageLive provides for Gemini, see the PageLive for Gemini documentation.
— End of Article —
Disclaimers
This analysis was conducted as part of the PageLive project, which develops keyboard shortcut and screen reader support for AI chat interfaces. The author develops PageLive, a Chrome extension that addresses several of the barriers described in this report. A companion Screen Reader Experience Mitigation documents the approaches PageLive applies to each finding.
PageLive can be installed for free on the PageLive chrome webstore page.
The findings, severity classifications, and testing observations in this report are the author's own, based on manual testing with NVDA on Chrome. AI assistance was used solely to shape the writing style of this document.
Top comments (0)