Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility issues for screenreader users #5187

Open
fcnjd opened this issue Jan 6, 2025 · 1 comment
Open

Accessibility issues for screenreader users #5187

fcnjd opened this issue Jan 6, 2025 · 1 comment
Labels
♿ a11y Accessibility

Comments

@fcnjd
Copy link
Contributor

fcnjd commented Jan 6, 2025

Hi,
instead of creating micro-issues, I believe it's better to sum up my accessibility findings from a screenreader user's perspective here centrally.

  • In the presets view, hover elements are used to show buttons to PIN or remove a preset, They're not keyboard-focusable. Those buttons should get labelled and focusable.
  • Prompts: In the prompt management, there are a lot of unlabelled buttons. I cannot tell for each one what it's supposed to do, but examples are buttons to rename or delete.
  • In the prompt createion field, every text box is labelled, there's however an unlabelled checkbox which I don't know what it's meant for.
  • In teh agent builder, after choosing model parameters, the button to save changes and get back to the builder is unlabelled. Same applies for the button to choose an avatar, or to get back from tools/agents view
  • When you add a tool to an agent that requires to enter an API key, the input box to open that key should automatically get focus. Otherwise, it just appears on top of the tools list, and I as the user wonder why nothing happens when I press the add button.
  • When pasting images into the chat, two unlabelled buttons appear: One to delete the image, and one that has the collapsed attribute - but nothing expands when pressed.
  • Online on the Code Interpreter website, the button to copy a created API key is unlabelled.
    Thank you very much for your work on making LibreChat more accessible. As an idea, I could imagine that integrating automatic test tools into the Pipeline such as Lighthouse CI could help to find such things faster, but that's just an idea of mine.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
♿ a11y Accessibility
Projects
None yet
Development

No branches or pull requests

3 participants