GitHub co-pilot is not informing screen reader users when it's applying code #147602
Replies: 4 comments 3 replies
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
Thank you very much AI for your input... |
Beta Was this translation helpful? Give feedback.
-
|
Quick updates: I played with the sound signals, specifically: These audio cues are set to auto by default. I switched them to on mode, but nothing changed. Of course, it’s not difficult for me to figure this out since I’m familiar with Co-Pilot and can recognize behaviors related to it. But for someone new, this might raise more questions than it answers. |
Beta Was this translation helpful? Give feedback.
-
|
Hello @snufas - thank you for taking the time to submit this feedback! To help the accessibility team better understand your reported issue, could you give us more information on which IDE extension, operating system, screen reader, and any additional information that might be helpful to know, when this occurs? Thanks so much! |
Beta Was this translation helpful? Give feedback.
-
|
I totally forgot that co-pilot is also available on other editors other than VSCode But anyway here are the details below: Version: 1.96.2 (system setup) I might as well add another suggestion First of all, the sound is way too long and feels like an error. Ideally, it should be a very short sound so it doesn't interrupt a screen reader while speaking. I know this might seem like nitpicking, but it’s definitely something that could be improved. While working with suggestions enabled, the only thing I hear is that constant, annoying sound. Ideally, it should be a short, subtle tick sound with no high frequencies, complementing the screen reader instead of being disruptive. It feels like someone just picked a random sound. Sure, it’s better than nothing, but honestly, it’s terrible. I am attaching a sound I think that would work quite well. It's short, non-obtrusive, can be even played repeatedly without annoyance. This sound can play anywhere from one to five times in a single line, so it needs to be very pleasant and non-intrusive. Right now, it’s the complete opposite of that. Coding with this sound is a terrible experience, and I ended up disabling suggestions because of it. I mean, I could disable the sound entirely, but the sound itself can be useful. It’s a good indicator, especially since I’ve disabled "speak suggestions." If I hear the sound and want a suggestion, I can investigate it. However, without the sound, I’d have to manually check all the suggestions, which disrupts my coding flow. I never wrote so much feedback for one simple sound... |
Beta Was this translation helpful? Give feedback.
-
|
Hello @snufas - thank you once again for bringing this issue to our attention. Our accessibility team was able to successfully reproduce the problem. Since this part of Copilot is managed by Microsoft, they have opened an issue in the VSCode repo with the details of your issue. You’re encouraged to follow up directly with the Microsoft team on the new issue and close out this one, but as always, feel free to reach out here if you need any further assistance! |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
Feedback on GitHub Copilot Accessibility
Hello,
I am a blind individual testing GitHub Copilot with a screen reader, and overall, it is quite accessible. The chat functionality works well, and there isn’t much that needs changing. However, I’ve noticed an issue when using the "Apply in Editor" button.
When I click "Apply in Editor", I lose track of the process. There is no clear indication of when the update starts or when it finishes. The only way I can tell the update is complete is when my cursor moves to the top of the code editor. It would be very helpful to have an audio notification or some other indicator to signal when the update begins and when it is done. A similar indicator to what is implemented in the chat would work well here.
Just to clarify, I am referring to the functionality where I click "Apply in Editor" in the chat window. I assume the same behavior applies in the inline chat as well.
Can you please also signal to me whether it's a good feedback and whether it will be applied in the next update? So I know at least that there is some progress going on.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions