Open derekjackson-das opened 4 days ago
Bro, I see that you brought up a bunch of a11y standards, involving issues like focus and contrast. If I were the repo author, I’d be super annoyed—you're nitpicking too much. Plus, the interface lost some aesthetics because of the contrast requirements. I have to commend the author for being very responsible, though, because no one is actually required to follow any so-called WCGA criteria.
@SailFlorve I understand your concerns but I am working closely with @derekjackson-das to improve accessibility and they are doing a huge service in pointing these issues out. It is my intention to make LibreChat the most accessible AI chat app there is, because as you said, there is no strict requirement to do this and even Claude.ai and ChatGPT have these shortcomings. This ultimately aligns with the mission of LibreChat to bring “Every AI for Everyone.”
I understand the concern for aesthetics but I think we’ve made some improvements in this regard. If there’s anything specific about the aesthetics you feel has changed negatively, please let me know. I personally am still learning how to make interfaces truly accessible and WCAG compliant and we don’t have to completely compromise on style in the process.
I'm worried that this might introduce a huge amount of extra complexity, bring in bugs, and potentially take a long time to troubleshoot and fix a11y issues. But you're right, it's truly meaningful for LibreChat to become the most a11y-friendly chat application. I really appreciate your efforts.
Issue Description: The low contrast on the toggle buttons in the Settings modal does not meet WCAG requirements. The toggle buttons in the "off" state do not have sufficient contrast for non-text elements. WCAG requires a minimum contrast of 3:1, but the contrast ratio is currently about 1.3:1. Since the buttons are not disabled but simply "off," they should meet the requirement for better accessibility. Low-vision users might find it difficult to identify and use the controls. This issue extends to other toggle buttons and some sliders in the application.
related to #4163
WCAG Criteria: 1.4.11 Non-text Contrast - AA
Screenshot:
Notes: This issue also occurs on other toggle buttons and some sliders across the application. Adding an outline to the toggle button or the entire control should be sufficient to meet the success criteria. For example: