Content on Images in Open source AI code editor screen is not visible properly in 100% mode: A11y_ Visual Studio Code Services_Open Source AI code editor screen _Functionality.
Maintainers usually reply within 1 day
@hawkticehurst is already working on this.
Since Feb 3, 2026.
- #9922 by @webdevpraveen — closed without merging
Assessment
This issue has not been assessed yet.
Description
GitHub Tags:
#A11yTCS; #DesktopWeb; #ChromiumEdge; #Win11; #A11yFunctional;
"Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification."
Environment Details:
Application Name: Visual Studio Code Services
URL: https://code.visualstudio.com
Chromium Edge: Version 144.0.3719.104 (Official build) dev (64-bit)
Edition: Windows 11 Enterprise Insider Preview
Version: 24H2
OS build: 26558.1000
Repro steps:
- Hit the URL: https://code.visualstudio.com
- Tab navigate to images present in the Open Source AI Code Editor Screen.
- Observe that Content on Images in Open source AI code editor screen is not visible properly in 100% mode.
Actual Result:
In the Open Source AI Code Editor screen, the content displayed on images is not visible or readable when viewed in the default 100% mode. This issue occurs due to poor contrast, overlapping content, or improper layout adjustments.
Expected Result:
All content on images should be clearly visible and readable in 100% mode. This includes ensuring sufficient contrast between text and background, proper alignment of content on images, and no overlapping or obscured elements.
User Impact:
Users will not be able to read the information completely from the images if the text is not visible completely at 100% mode.
Attachment:
https://github.com/user-attachments/assets/91684e4b-1e06-49a5-a9ce-4e93014f2856
- Dominant language
- Markdown
- Stars
- 6.7k
- Forks
- 5.8k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 138
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-docs
-
triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
microsoft/vscode-docs#10626 ·
Maintainers usually reply within 1 day
-
Agent plugin migration: gaps in package conversion, canvas discovery, and hook stdout guidancePossibly taken @jebakishore509-sys claimed this 12 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 54/100
microsoft/vscode-docs#10551 ·
Maintainers usually reply within 1 day
-
doc-enhancement
Difficulty 1/5 Under an hour Newbie friendliness 45/100
microsoft/vscode-docs#10526 · 1 reaction ·
Maintainers usually reply within 1 day
-
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds (span:nth-child(6)):A11y_code.visualstudio.com_AI4WMay be free again @ntrogh claimed this 38 days ago, and no pull request is open. Open
microsoft/vscode-docs#10424 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
idea
Difficulty 3/5 1-2 days Newbie friendliness 45/100
microsoft/vscode-docs#10216 · 1 comment ·
Maintainers usually reply within 1 day