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
[Accessibility] Semantic heading tag is missing in issue and PR webview comments #5524
Labels
accessibility
bug
Issue identified by VS Code Team member as probable bug
verified
Verification succeeded
Comments
meganrogge
added
bug
Issue identified by VS Code Team member as probable bug
accessibility
labels
Nov 30, 2023
This is cool. I didn't know screen readers did this. |
Strong tag is not a semantic tag. It’s rather a formatting tag. For screen reader users, please replace it with h3 semantic tag.
|
For comment threads in the editor we have commands with keybindings: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
accessibility
bug
Issue identified by VS Code Team member as probable bug
verified
Verification succeeded
Type: Bug
CC @meganrogge
If screen reader users open any GitHub issue or PR containing multiple comments in VSCode, SR users expect to jump between comments by using semantic heading. On gitHub webpage, each commentor name is denoted with h3 tag. However, currently, VSCode GH extension does not have the h3 tag for commentors name so it's hard to navigate between comments.
Extension version: 0.77.2023112911
VS Code version: Code - Insiders 1.85.0-insider (8762127fc97b8aaae5f3a0dd6a6d853d9a1b7574, 2023-11-29T17:38:23.440Z)
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
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: