Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #1022] [BUG]: Many controls lack screen reader labels #630

New Issue
Closed
opened 2026-02-22 18:20:34 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:20:34 -05:00
Owner
Copy Link
Copy Source

Originally created by @cartertemm on GitHub (Apr 2, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1022

How are you running AnythingLLM?

Local development

What happened?

Currently, when screen reading software like NVDA (non-visual desktop access) is used to navigate the UI, it is difficult to deduce what many of the buttons and links do.

This is because they are denoted by icons, not text. It would be extremely beneficial for blind users to supply labels for UI controls that can supplement the icons.
With ARIA, these modifications wouldn't need to alter or inhibit the current layout in any way. The simplest improvements that I envision would be:

  • Label the back button on the onboarding screen
  • Label the continue button on the onboarding screen
  • Label the social links, which are currently only represented by images
  • Label some of the navigation items (general appearance, settings button)
  • Indicate the currently selected workspace to screen readers, and mark up the relationship as a list container for quick navigation
  • Indicate the currently selected thread to screen readers, and mark up the relationship as a list container for quick navigation
  • Label the button that shows thread options
  • Label copy and thumb up/down buttons in a chat
  • Label stop generating button

Are there known steps to reproduce?

I can provide more info if requested.

Originally created by @cartertemm on GitHub (Apr 2, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1022 ### How are you running AnythingLLM? Local development ### What happened? Currently, when screen reading software like [NVDA (non-visual desktop access)](https://github.com/nvaccess/nvda) is used to navigate the UI, it is difficult to deduce what many of the buttons and links do. This is because they are denoted by icons, not text. It would be extremely beneficial for blind users to supply labels for UI controls that can supplement the icons. With ARIA, these modifications wouldn't need to alter or inhibit the current layout in any way. The simplest improvements that I envision would be: * Label the back button on the onboarding screen * Label the continue button on the onboarding screen * Label the social links, which are currently only represented by images * Label some of the navigation items (general appearance, settings button) * Indicate the currently selected workspace to screen readers, and mark up the relationship as a list container for quick navigation * Indicate the currently selected thread to screen readers, and mark up the relationship as a list container for quick navigation * Label the button that shows thread options * Label copy and thumb up/down buttons in a chat * Label stop generating button ### Are there known steps to reproduce? I can provide more info if requested.
yindo added the possible bug label 2026-02-22 18:20:34 -05:00
yindo closed this issue 2026-02-22 18:20:34 -05:00
yindo commented 2026-02-22 18:20:34 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Apr 2, 2024):

🙏 ! Thank you for raising this (and i see the PR now too). Will review tomorrow

@timothycarambat commented on GitHub (Apr 2, 2024): 🙏 ! Thank you for raising this (and i see the PR now too). Will review tomorrow
yindo changed title from [BUG]: Many controls lack screen reader labels to [GH-ISSUE #1022] [BUG]: Many controls lack screen reader labels 2026-06-05 14:36:22 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#630
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?