microsoft / microsoft/vscode-docs

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.

Open
#9,312 1 comment 0 reactions 1 assignee View on GitHub

@hawkticehurst is already working on this.

Since Feb 3, 2026.

accessibility
Dominant language
Markdown
Stars
6.6k
Forks
5.8k
Avg merge
11h 43m
Merged PRs (30d)
123

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:
  1. Hit the URL: https://code.visualstudio.com
  2. Tab navigate to images present in the Open Source AI Code Editor Screen.
  3. 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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.