Consider how we might improve navigation to chat response content for screen reader users #228599
Labels
accessibility
Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues
bug
Issue identified by VS Code Team member as probable bug
under-discussion
Issue is under discussion for relevance, priority, approach
Milestone
@jooyoungseo has been interacting with the rendered HTML version of our chat responses more recently because of the introduction of the helpful hyperlinks.
He mentioned that there are several tab stops that are encountered before a screen reader user reaches the content of a chat response:
He suggested that at least for windows/linux users, adding the
role=document
would help here. This wouldn't help macOS users and we probably want a solution that solves this for all platforms.Another idea he had was to add a heading to the content so when a user enters a mode of their screen reader, they can go to it directly.
I mentioned that we're thinking about moving the toolbar (not sure about the references) to the bottom of the response. He raised concerns about the discoverability of the toolbar in that case for screen reader users but suggested that he has long thought a right click context menu would be advantageous and discoverable for users.
@roblourens or @rperez030 any thoughts?
The text was updated successfully, but these errors were encountered: