[Accessibility] Use aria-live instead of auto synth for Chat response to typed query #229062
Labels
accessibility
Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues
feature-request
Request for new features or functionality
Milestone
Type: Bug
CC @meganrogge
Currently, auto synth read-aloud is used universally in Chat for both voice and manual query when screen reader mode is on whereas non-SR users hear the auto synth only when the voice query is used:
Please disable auto synth read-aloud and use aria-live for manual query for SR users. This is because SR users may want to intentionally (and selectively) use the auto synth read-aloud just like sighted users. Non-SR users may easily think that the auto synth read-aloud and aria-live provide the same result; however, that's not the case. SR's TTS is a more customized speech output (e.g., rate; volume; voice color) while the auto synth read-aloud is a factory (less configurable) output. We have to carefully avoid any overgeneralization under a simple assumption that the two methods share the same audio modality. Based on my experience over the past couple of days, I feel like using aria-live for manual query and auto synth read-aloud for voice query has been more preferrable and offered a more pleasant experience.
VS Code version: Code - Insiders 1.94.0-insider (8d1bb84, 2024-09-19T05:04:09.996Z)
OS version: Windows_NT x64 10.0.22631
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Extensions (125)
(1 theme extensions excluded)
A/B Experiments
The text was updated successfully, but these errors were encountered: