Placeholder text contrast is below 4.5:1 for “Enter Your Answer” input field in Light and Dark (2026) theme:A11y_VisualStudioCode_Improved UI for MCP elicitation_Keyboard
@mrleemurray is already working on this.
Since Jun 12, 2026.
Assessment
This issue has not been assessed yet.
Description
GitHub Tags
#A11yTCS;#Visual Studio Code Client; #SH_Integrated browser features_Win32_JUNE2026;#DesktopApp;#FTP;#Win32;#A11ySev3;#A11yMAS;#WCAG1.4.3; #ES Chat_Deeplink; #Contrast; #SCIM:Bug5430506;
Issue Subcategory
Placeholder text insufficient contrast
User Experience
Users with low vision cannot read placeholder text that provides input hints or instructions. They may not understand what data to enter in the field.
Repro Steps
Open VS Code > Trigger an elicitation form in copilot chat > Enter your answer > Observe the issue: Placeholder text contrast is below 4.5:1 for “Enter Your Answer” input field in Light and Dark (2026) theme
Actual Result
The placeholder text “Enter Your Answer” in the input field has insufficient color contrast against its background in both Light and Dark (2026) themes. The observed contrast ratio is below 4.5:1, causing the text to appear faint and difficult to read.
Expected Result
Placeholder text should have a minimum contrast ratio of 4.5:1.
How to Fix
Increase the contrast of placeholder text via ::placeholder CSS. Better yet, use persistent visible labels above or beside the input rather than relying on placeholders alone.
Environment details
Application Name: VS Code
VS Code version: 1.124.2
Edition Windows 11 Enterprise
Version 25H2
OS build 26200.8390
Note:
- Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification.
- Try ES Chat to learn more about the MAS rule and how to fix the issue. If you need more help, use our Teams channel or office hours.
- "Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."
Attachment
- Dominant language
- TypeScript
- Stars
- 193k
- Forks
- 42.9k
- PR merge metrics
- PR metrics pending
Contributor 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
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
new release
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
All issues in microsoft/vscode
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·