Skip to content
| Marketplace
Sign in
Visual Studio Code>Linters>A11yResolverNew to Visual Studio Code? Get it now.
A11yResolver

A11yResolver

Preview

A11Y Solutions

|
12 installs
| (0) | Free
AI-powered accessibility agent. Beta preview.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

A11yResolver

Ship accessible code by default — not after audits or rework.

Detect, fix, and validate accessibility issues directly in your editor with AI — before your code reaches production.

Fix accessibility issues automatically with a single command.

A11yResolver is an AI-powered accessibility agent that detects, refactors, and validates your code to meet WCAG standards right inside VS Code.

Preview / Beta

This extension is under active development. The experience may evolve rapidly based on user feedback, and some features may change.

What it does

  • Automatically detects and fixes accessibility issues such as missing labels, low contrast, keyboard traps, and more by intelligently refactoring components.
  • Validates with real user interaction in its built-in browser by simulating keyboard navigation, testing dynamic UI behavior, and catching issues that static analysis misses.
  • Refactors code through a conversational agent — describe what you need or let it propose and apply changes.
  • Remembers your session so you can continue exactly where you left off.

1-Command Magic Example

Fix all accessibility issues in this component

Result:

  • ✔ Added proper accessible labels and alt text
  • ✔ Replaced non-semantic elements with correct structure
  • ✔ Enabled full keyboard navigation
  • ✔ Improved ARIA attributes for screen readers

Why this matters

Most accessibility issues surface late — after development, during audits, or post-launch — causing expensive rework, delayed releases, failed compliance audits, and legal/reputational risk.

A11yResolver prevents this by making accessibility part of your daily workflow. Accessibility is no longer a final step — it’s built in from the start.

Unlike traditional accessibility tools that only scan and suggest, A11yResolver actively fixes and validates issues — including real-browser interaction.

Getting started (Quick & Simple)

  1. Install the extension.
  2. Open the A11yResolver panel.
  3. Add your OpenRouter API key.
  4. Start fixing accessibility instantly.

Agents

  • Issues Resolver (Fast) — Best for everyday fixes, quick iteration, lower cost
  • Issues Resolver Expert — Best for complex issues, deeper analysis, stubborn problems

Tip: Start with Fast. Switch to Expert when you need more reasoning power.

Browser Validation (your hidden superpower)

  • Simulate real keyboard navigation
  • Test dynamic and stateful UI behavior
  • Catch runtime accessibility issues that pure static tools miss

Anonymous telemetry

This extension supports a basic, privacy-respecting telemetry mode to help understand feature adoption and improve stability.

What it helps us understand:

  • Extension activation
  • Chat usage
  • Live Browser usage
  • Issues sheet usage
  • Issue-resolution requests
  • Selected agent type

What it does not collect:

  • Prompts or chat contents
  • Source code
  • File paths
  • API keys
  • Personal identifiers

Why this exists:

  • It helps us learn which features are useful and where the product needs improvement
  • It is designed to run quietly in the background without slowing down your workflow
  • It uses an anonymous identifier stored locally in VS Code

Opt out

To disable telemetry for this extension, turn off telemetry in VS Code. The extension respects vscode.env.isTelemetryEnabled automatically.

If you prefer, you can also disable the telemetry endpoint setting for the extension.

Notes

  • A valid OpenRouter API key is required for AI features.
  • Built by accessibility experts with real-world WCAG audit and remediation experience across enterprise projects.
  • Some tasks can run in the extension's internal browser. To use that capability, Google Chrome must be installed on your machine. Microsoft Edge is supported as an automatic fallback. If the browser fails to launch even though Chrome is installed (a known Windows edge case), set the absolute path in Settings → Extensions → A11yResolver → Chrome Path.
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft