github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-23 14:13:13 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #11806] Accessibility issues with screen readers in Ollama for Windows #7833

New Issue
Open
opened 2026-04-12 20:00:09 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-12 20:00:09 -05:00
Owner
Copy Link

Originally created by @dreinn on GitHub (Aug 8, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11806

Originally assigned to: @hoyyeva on GitHub.

What is the issue?

When visually impaired users attempt to use the Ollama app for Windows, there are several accessibility issues with screen readers.
I am using NVDA, but the same problems occur with other screen readers.

Steps to Reproduce:

  1. Open Ollama for Windows with a screen reader active (e.g., NVDA).
  2. Navigate through the main window and settings tab.

Observed Issues:

Main window:

  • The “Toggle web search” button does not expose its state (on/off) to the screen reader. Suggest changing its control type from Button to ToggleButton so its state can be announced.
  • The “gpt-oss:20b” button is labeled correctly (no issue here).
  • Another button has no label at all (possibly the send button).

Settings tab:

  • There is an unlabeled button that acts as “Close” for the settings tab.
  • It is not possible for a visually impaired user to know which Context length option is selected (e.g., “4k”, “8k”, etc.), as the active state is not exposed to the screen reader.

Expected Behavior:

  • All buttons should have accessible labels.
  • Toggle controls should expose their state to assistive technologies.
  • Selected options should be announced by the screen reader.

Environment:

  • Ollama for Windows (version 0.11.3)
  • NVDA screen reader (latest version)
  • Windows 11

Relevant log output

OS

Windows

GPU

Nvidia

CPU

Intel

Ollama version

0.11.3

Originally created by @dreinn on GitHub (Aug 8, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11806 Originally assigned to: @hoyyeva on GitHub. ### What is the issue? When visually impaired users attempt to use the Ollama app for Windows, there are several accessibility issues with screen readers. I am using NVDA, but the same problems occur with other screen readers. **Steps to Reproduce:** 1. Open Ollama for Windows with a screen reader active (e.g., NVDA). 2. Navigate through the main window and settings tab. **Observed Issues:** **Main window:** * The **“Toggle web search”** button does not expose its state (on/off) to the screen reader. Suggest changing its control type from `Button` to `ToggleButton` so its state can be announced. * The **“gpt-oss:20b”** button is labeled correctly (no issue here). * Another button has no label at all (possibly the send button). **Settings tab:** * There is an unlabeled button that acts as “Close” for the settings tab. * It is not possible for a visually impaired user to know which **Context length** option is selected (e.g., “4k”, “8k”, etc.), as the active state is not exposed to the screen reader. **Expected Behavior:** * All buttons should have accessible labels. * Toggle controls should expose their state to assistive technologies. * Selected options should be announced by the screen reader. **Environment:** * Ollama for Windows (version 0.11.3) * NVDA screen reader (latest version) * Windows 11 ### Relevant log output ```shell ``` ### OS Windows ### GPU Nvidia ### CPU Intel ### Ollama version 0.11.3
GiteaMirror added the appbug labels 2026-04-12 20:00:09 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label app bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#7833
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?