mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 10:58:17 -05:00
[GH-ISSUE #1001] feat: screen reader #12290
Reference in New Issue
Block a user
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?
Originally created by @mhussaincov94 on GitHub (Mar 2, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/1001
Bug Report
Description
I downloaded the new image of open-webui deleted the old container deleted the ollama-webui container and recreated a new image from main of open-webui.
none of the buttons that were labled before such as new chat dockuments genneral advanst are labled for a screen reader.
I am no longer able to use open-webui in it's current form.
Bug Summary:
[Provide a brief but clear summary of the bug]
buttons that were labled before are no longer labled.
Steps to Reproduce:
[Outline the steps to reproduce the bug. Be as detailed as possible.]
1.
runn the latest image of open-webui.
log in to the webui.
2.
run orca screen reader on linux.
3.
try navigateing around the page using the tab key and the shift tab key.
Expected Behavior:
[Describe what you expected to happen.]
I expect buttons to be read out to me such as new chat push button, dockuments pushbutton etc.
Actual Behavior:
[Describe what actually happened.]
when tabbing around the interface the only thing my screen reader orca says now is,
push button
push button.
I would be greatful if you could look in to this.
I would say this is ergent because currently I am unable to use the web-ui in it's current form without labled buttons.
Environment
Operating System: [e.g., Windows 10, macOS Big Sur, Ubuntu 20.04]
debian unstable with all updates installed with docker chromeium latest.
Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0]
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
[Describe the method you used to install the project, e.g., manual installation, Docker, package manager, etc.]
docker
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
@jyaru1110 commented on GitHub (Feb 14, 2025):
Is anyone working on this? I could help here.
@tjbck commented on GitHub (May 24, 2025):
#2790