I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
v0.8.11 - v0.9.2
Ollama Version (if applicable)
0.21.0
Operating System
Debian 13 Gnome
Browser (if applicable)
Firefox & Chromium
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
Expected Behavior
UI Should be Accessable with screenreader
Actual Behavior
UI Ellements are not acessable with Screenreader from v0.8.11
Steps to Reproduce
Docker Image: ghcr.io/open-webui/open-webui:main
OS: Linux Debian 13 (GNOME)
Screen Reader: Orca
Browsers tested: Firefox, Chromium
Display Server: Reproduced on both Wayland and X11
Logs & Screenshots
Additional Information
Description
Keyboard navigation (using Tab or arrow keys) worked perfectly up until version v0.8.10. Since upgrading to v0.8.11, certain UI elements can no longer be reached via screen reader.
Specifically, the user menu (used for logging out or accessing settings) is no longer accessible. This affects both the menu in the top-right corner and the menu in the bottom-left corner. Even toggling the sidebar does not resolve the issue; the menus remain unreachable. Furthermore, the buttons for uploading files, activating tools, and enabling web search cannot be reached via Tab or arrow keys. Instead, the screen reader focus jumps directly from the chat input field to the voice input button.
Because these buttons cannot be reached via keyboard, they are inaccessible to blind or low-vision users.
Environment
Docker Image: ghcr.io/open-webui/open-webui:main
OS: Linux Debian 13 (GNOME)
Screen Reader: Orca
Browsers tested: Firefox, Chromium
Display Server: Reproduced on both Wayland and X11
Reproduction/Verification
To ensure the issue was not caused by the screen reader itself, I downgraded Open WebUI to v0.8.10, where navigation worked without any issues. This confirms the bug was introduced in v0.8.11.
Affected Versions
All versions from v0.8.11 up to (and including) v0.9.2.
Additional Notes
While there are other minor accessibility issues (e.g., selecting the menu to edit folders in the sidebar or using the model selector), these have existed previously and can be managed with certain workarounds. However, this new bug makes the application practically unusable for blind users.
The attached screenshots highlight the areas that were still accessible in v0.8.10.
Thank you for your help! Additional testing on other operating systems or screen readers would be greatly appreciated.
Originally created by @martin-schmit on GitHub (Apr 24, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24097
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.8.11 - v0.9.2
### Ollama Version (if applicable)
0.21.0
### Operating System
Debian 13 Gnome
### Browser (if applicable)
Firefox & Chromium
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
UI Should be Accessable with screenreader
### Actual Behavior
UI Ellements are not acessable with Screenreader from v0.8.11
### Steps to Reproduce
Docker Image: ghcr.io/open-webui/open-webui:main
OS: Linux Debian 13 (GNOME)
Screen Reader: Orca
Browsers tested: Firefox, Chromium
Display Server: Reproduced on both Wayland and X11
### Logs & Screenshots
<img width="2256" height="1504" alt="Image" src="https://github.com/user-attachments/assets/0b6acea7-b667-4227-9b2b-8dc86cc38a89" />
<img width="2256" height="1504" alt="Image" src="https://github.com/user-attachments/assets/5661bb89-2607-4c40-9fd9-4162c0fea25a" />
<img width="2256" height="1504" alt="Image" src="https://github.com/user-attachments/assets/19ae0b65-9200-42da-8c2f-ef9c6c4f20eb" />
<img width="2256" height="1504" alt="Image" src="https://github.com/user-attachments/assets/61fef66a-af89-4d75-9997-34b05157e906" />
### Additional Information
Description
Keyboard navigation (using Tab or arrow keys) worked perfectly up until version v0.8.10. Since upgrading to v0.8.11, certain UI elements can no longer be reached via screen reader.
Specifically, the user menu (used for logging out or accessing settings) is no longer accessible. This affects both the menu in the top-right corner and the menu in the bottom-left corner. Even toggling the sidebar does not resolve the issue; the menus remain unreachable. Furthermore, the buttons for uploading files, activating tools, and enabling web search cannot be reached via Tab or arrow keys. Instead, the screen reader focus jumps directly from the chat input field to the voice input button.
Because these buttons cannot be reached via keyboard, they are inaccessible to blind or low-vision users.
Environment
Docker Image: ghcr.io/open-webui/open-webui:main
OS: Linux Debian 13 (GNOME)
Screen Reader: Orca
Browsers tested: Firefox, Chromium
Display Server: Reproduced on both Wayland and X11
Reproduction/Verification
To ensure the issue was not caused by the screen reader itself, I downgraded Open WebUI to v0.8.10, where navigation worked without any issues. This confirms the bug was introduced in v0.8.11.
Affected Versions
All versions from v0.8.11 up to (and including) v0.9.2.
Additional Notes
While there are other minor accessibility issues (e.g., selecting the menu to edit folders in the sidebar or using the model selector), these have existed previously and can be managed with certain workarounds. However, this new bug makes the application practically unusable for blind users.
The attached screenshots highlight the areas that were still accessible in v0.8.10.
Thank you for your help! Additional testing on other operating systems or screen readers would be greatly appreciated.
GiteaMirror
added the bug label 2026-04-25 09:53:37 -05:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @martin-schmit on GitHub (Apr 24, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24097
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.8.11 - v0.9.2
Ollama Version (if applicable)
0.21.0
Operating System
Debian 13 Gnome
Browser (if applicable)
Firefox & Chromium
Confirmation
README.md.Expected Behavior
UI Should be Accessable with screenreader
Actual Behavior
UI Ellements are not acessable with Screenreader from v0.8.11
Steps to Reproduce
Docker Image: ghcr.io/open-webui/open-webui:main
OS: Linux Debian 13 (GNOME)
Screen Reader: Orca
Browsers tested: Firefox, Chromium
Display Server: Reproduced on both Wayland and X11
Logs & Screenshots
Additional Information
Description
Keyboard navigation (using Tab or arrow keys) worked perfectly up until version v0.8.10. Since upgrading to v0.8.11, certain UI elements can no longer be reached via screen reader.
Specifically, the user menu (used for logging out or accessing settings) is no longer accessible. This affects both the menu in the top-right corner and the menu in the bottom-left corner. Even toggling the sidebar does not resolve the issue; the menus remain unreachable. Furthermore, the buttons for uploading files, activating tools, and enabling web search cannot be reached via Tab or arrow keys. Instead, the screen reader focus jumps directly from the chat input field to the voice input button.
Because these buttons cannot be reached via keyboard, they are inaccessible to blind or low-vision users.
Environment
Docker Image: ghcr.io/open-webui/open-webui:main
OS: Linux Debian 13 (GNOME)
Screen Reader: Orca
Browsers tested: Firefox, Chromium
Display Server: Reproduced on both Wayland and X11
Reproduction/Verification
To ensure the issue was not caused by the screen reader itself, I downgraded Open WebUI to v0.8.10, where navigation worked without any issues. This confirms the bug was introduced in v0.8.11.
Affected Versions
All versions from v0.8.11 up to (and including) v0.9.2.
Additional Notes
While there are other minor accessibility issues (e.g., selecting the menu to edit folders in the sidebar or using the model selector), these have existed previously and can be managed with certain workarounds. However, this new bug makes the application practically unusable for blind users.
The attached screenshots highlight the areas that were still accessible in v0.8.10.
Thank you for your help! Additional testing on other operating systems or screen readers would be greatly appreciated.