-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[BUG] Accessibility Issue with DeepSeek v3 - Impossible reCAPTCHA for Blind Users #220
Comments
I have helped you to feedback this problem to the official team, the official team said they are focusing on how to solve this problem (sic: we are focusing on how to optimize this verification process, thanks for the feedback), before long should be solved this problem. |
Thank you for your efforts. Could you possibly help me communicate with the relevant team via email? |
Hi @khsbory, Thanks for sharing this issue and explaining it so clearly—it was super helpful! While I’m not officially part of the DeepSeek team, I’ve taken a shot at solving the problem you reported. I’ve submitted a pull request to address this: Improve Accessibility for CAPTCHA Challenges in DeepSeek v3. Once the DeepSeek team reviews and merges the changes, you should be able to sign up and log in without any issues. I’d love to hear how it works for you once it’s live—your feedback would mean a lot! Thanks again for raising this—it’s a step toward making DeepSeek better for everyone. 😊 |
Wow, I'm truly touched by your willingness to collaborate and help resolve this issue, even though you're not officially part of the DeepSeek team. |
Currently the official may not have more time to reply to my question, but if you want to use Deepseek model, I can provide you with a link which is the link to jump to gmail login after image validation (at present the test is less than 2 hours to directly click on the login will not be triggered by the authentication code, I have already tested it) you can directly login to their gmail can be used! The downside is that this url can only be used once. |
Wow, thanks to you, I successfully logged into DeepSeek. I'm currently exploring and using it actively. As a temporary workaround, I'll make sure not to log out on this PC. However, I hope this issue remains open until the accessibility of the security CAPTCHA is improved. Thank you! |
Thank you for reaching out and for your patience. We sincerely apologize for the delayed response. We acknowledge receiving your email and have conducted internal discussions regarding your concerns. While we understand your desire for a complete software experience, we're currently unable to provide a satisfactory solution at this time. The implementation of complex CAPTCHA verification is a necessary security measure we've had to adopt due to severe reverse engineering attacks we're currently facing. This was not a decision we made lightly, but rather a crucial step to protect our system and users. We fully support and appreciate your initiative to enhance the user experience with DeepSeek V3. While we're actively working towards a more elegant solution that would enable barrier-free access for all users, our current resources (both human and technical) prevent us from committing to a specific timeline. However, please rest assured that this matter remains a priority on our development roadmap. Regarding your other issue, we've taken note of it and are exploring potential solutions. Thank you for your understanding and continued support. We truly value your feedback and are committed to improving our product for all users. |
Thank you for your kind response. Yesterday, while using the DeepSeek service, I realized it's an incredible solution that could potentially double my work efficiency. While I don't want to rush you, let's work together to improve its accessibility. A great service is even more valuable when it can be used by people with disabilities. Currently, I have two laptops. I was able to successfully log in on one of them thanks to the temporary login link you provided two days ago. Could you please provide a similar link for my other laptop? This laptop is the one I use in my office, and since I work alone, I need your help with this. Once you provide the link, I will use it immediately for logging in. Thank you! |
Just reporting that I'm not visually impaired, yet the Google login workflow was broken for me, I think because of the captcha (despite solving it correctly several times). The above link let me log in without the captcha. Thanks! |
Hello, Best regards 您好, 顺祝安好 |
Hi everyone,
I'm a visually impaired user who is very interested in trying out the DeepSeek v3 web service.
As a blind user, I rely on the NVDA screen reader to access websites.
For this to work, websites need to be designed with accessibility in mind.
I'm running into a major roadblock when trying to sign up for DeepSeek v3.
After attempting to log in with Google, I'm faced with a reCAPTCHA security challenge that is completely inaccessible to me.
The reCAPTCHA displays an image and requires me to "Click on the smallest yellow sphere in the picture."
As a screen reader user, I have no way of perceiving or interacting with this image-based challenge, making it impossible for me to create an account.
It is essentially locking me out of the service.
I understand the need for security measures, but this particular reCAPT সৃষ্টির CAPTCHA implementation completely disregards the needs of visually impaired users.
I have tried to reach DeepSeek directly using the email address [email protected].
However, until now I did not receive any response.
I'm hoping someone in this community can help me connect with the right person at DeepSeek to address this significant accessibility barrier.
Ideally, they could implement an alternative, accessible authentication method for users who cannot complete visual CAPTCHAs.
I'm very keen to use DeepSeek v3 and hope that with your help, we can make it accessible to everyone.
Thank you for your time and any assistance you can offer.
The text was updated successfully, but these errors were encountered: