You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am a visually impaired user who relies on a screen reader to interact with DeepSeek v3. I've identified an accessibility issue with the toggle buttons in the chat interface that needs attention.
Current Issue
On the DeepSeek chat page, there are two toggle buttons for "Search" and "Deep Think" functionalities. While these buttons allow users to enable/disable their respective features, their current state (on/off) is not properly announced by screen readers. This makes it impossible for screen reader users to know whether a feature is currently enabled or disabled.
Proposed Solution
This accessibility issue can be easily resolved by implementing the aria-pressed attribute on the toggle buttons. The attribute should dynamically update between true and false based on the button's state.
Implementation Details
Here's a Next.js implementation example for accessible toggle buttons:
Screen readers will announce these elements as toggle buttons
The current state (pressed/not pressed) will be properly announced
Users will receive clear feedback about the feature's state when navigating the interface
Benefits
This enhancement will significantly improve the user experience for visually impaired users while maintaining the existing functionality for all users.
Could you please implement this accessibility enhancement in the next update?
Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered:
Hello,
I am a visually impaired user who relies on a screen reader to interact with DeepSeek v3. I've identified an accessibility issue with the toggle buttons in the chat interface that needs attention.
Current Issue
On the DeepSeek chat page, there are two toggle buttons for "Search" and "Deep Think" functionalities. While these buttons allow users to enable/disable their respective features, their current state (on/off) is not properly announced by screen readers. This makes it impossible for screen reader users to know whether a feature is currently enabled or disabled.
Proposed Solution
This accessibility issue can be easily resolved by implementing the
aria-pressed
attribute on the toggle buttons. The attribute should dynamically update betweentrue
andfalse
based on the button's state.Implementation Details
Here's a Next.js implementation example for accessible toggle buttons:
Expected Behavior
With this implementation:
Benefits
This enhancement will significantly improve the user experience for visually impaired users while maintaining the existing functionality for all users.
Could you please implement this accessibility enhancement in the next update?
Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered: