-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
Screen reader announcement for chat response is too verbose #212788
Comments
Btw I have a similar challenge for the text-to-speech integration where I am thinking about converting the markdown string to a plain text string using
But I did notice that this would remove some text, such as ordered list. |
@alexdima made a good point in our standup today: why are we not leveraging the HTML screen reader support for chat items but use
|
The HTML screen reader support requires users to enter different modes to navigate - browse/focus mode. Feedback from screen reader users suggested this is not user friendly. Users will examine content in detail in the chat accessible view, not here. Providing an overview of the response with aria alert is desired. This is similar to how sighted users see the response streaming in. Screen reader users press escape if they don't wish to hear the content. |
I agree it's not good that it's reading the full URLs. A similar problem is here #210665 and my solution to that will be to remove those links and provide an alternate way of setting any keybindings which are undefined. |
Potential verification found: I asked for the location of some code, and after Copilot finished typing out the response, it announced the entire response, including all the link text and full command IDs. |
LGTM now. I might've forgotten to update something. |
A screenshot of the text that was announced would help to know if this was fixed or not @rzhao271 |
unclear how this could be happening as I'm using
|
figured it out |
@meganrogge It is still reading the complete path for me. |
going to see if I can repro on windows |
Have a response that contains references to code, e.g. :
Start screen reader and click on the response. Notice how the full URLs are being read out aloud which are very long.
Verbatim text:
I think this stems from the fact that we just take the response as string here:
vscode/src/vs/workbench/contrib/chat/browser/chatAccessibilityService.ts
Line 35 in ffb2581
The text was updated successfully, but these errors were encountered: