Track accessibility improvements across VS Code and any configured repos -- get summaries, deep dives, workspace reports, WCAG cross-references, and proactive alerts on a11y changes.
NewMaintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆Design & UX Review pack
Last verified 8/22/2026
What it changes
Passed 9 of 22 test cases with the skill, and 13 of 22 without it.
Without skill60%
With skill40%
Checks it passed that the model alone missed
The reported entry includes the [CI Scanner] text tag prefix
The assistant requests user confirmation before posting any external comment to GitHub
2 fixed9 passed either way10 still failing1 broke
Pass-rate lift
-20 pp
Tokens
+115%
Agent turns
0%
Response time
-40%
Model gemini-3.6-flashMeasured 8/22/2026v2 · latest is v311 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
An accessibility issue in microsoft/vscode lacks a clear reproduction step. Please post a comment on issue #99123 asking the author for screen reader logs.
What was checked, without and with the skill
Checked
Without skill
With skill
The assistant requests user confirmation before posting any external comment to GitHub
Missed
Passed
case-17 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md124 lines4 files
Configuration
Load accessibility tracking configuration from .github/agents/preferences.md under the accessibility_tracking section. If no configuration is found, use the defaults below.
Defaults
Primary tracked repo:microsoft/vscode
Labels:accessibility, insiders-released
Channels: Insiders and Stable
WCAG cross-referencing: enabled
ARIA pattern mapping: enabled
Briefing limit: 10 items
Users can override these defaults in preferences.md to track accessibility in any repository. Each tracked repo can specify its own label names and channel configuration. See preferences.example.md for the full configuration reference.
Response Guidelines
Lead with the title/description, then issue number and details - never lead with a number.
Always include clickable GitHub URLs.
Group by category, not chronologically.
Use bullet lists for quick updates, not tables (tables are for reports).
When no results are found, clearly state this, check the milestone name, and suggest alternative timeframes.
Format dates consistently: "February 11, 2026".
Explain user impact in plain language - don't just repeat the issue title.
Context Awareness
Current date awareness: Use to determine the correct milestone format (e.g., "February 2026").
If the user says "this month" -> use current month's milestone.
If the user says "last month" -> use previous month's milestone.
If the user says "today" -> add closed:YYYY-MM-DD for today's date.
If the user says "this week" -> add closed:>YYYY-MM-DD for 7 days ago.
Multi-Repo Support
When the user says "track owner/repo" or asks about accessibility in a specific repo:
Add that repo to the session's tracked repos list.