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.
Works on VS Code, Windsurf, Cursor, and compatible IDEs Beta
Free during beta · Subscription pricing coming soon
What it does
Detect, fix, and validate accessibility issues where code gets written
A11yResolver helps developers move from accessibility findings to working fixes directly in VS Code — with AI-assisted remediation and real-browser validation built into the workflow.
Validate fixes in a real browser, not just in static code
A11yResolver can test changes through real browser interaction, including keyboard navigation, focus behavior, dynamic states, and UI patterns that static analysis often misses.
- Keyboard navigation simulation
- Focus management checks
- Dynamic ARIA/state validation
- Runtime issues beyond static scanning
Detect issues and apply code-aware fixes
Find accessibility issues in context and let the agent propose or apply targeted code changes across components, patterns, and files.
Missing accessible name → adds label while preserving component behavior.
Remediate through a conversational agent
Ask the agent to explain, adjust, or apply a fix. Developers can guide the remediation instead of manually searching through the codebase.
Keep context while you work
A11yResolver remembers the active session so developers can continue across related issues without restarting the investigation.
Browser validation
The hidden superpower: validate accessibility through real interaction
This helps teams catch issues that only appear during actual interaction — not just in static code review.
- Simulate real keyboard navigation
- Test dynamic and stateful UI behavior
- Catch runtime accessibility issues that pure static tools miss
1-command example
Fix accessibility issues automatically with a single command
Changes applied
- Unlabeled icon button
- Input without label
- Modal without focus trap
Why it matters
Accessibility issues are expensive when they surface late
Most accessibility issues surface late — after development, during audits, or post-launch — causing expensive rework, delayed releases, failed compliance audits, and legal or 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.
Late discovery (status quo)
- Issues found during QA or audit
- Developer re-opens completed work
- Sprint velocity impacted
- Compliance gaps delay releases
- Rework compounds technical debt
Built-in workflow (A11yResolver)
- Issues caught in the editor, before commit
- Fixes applied automatically in context
- No disruption to development flow
- Compliance built in from the start
- Validated with real browser interaction
Real impact
50–70% faster resolution, from day one
From an experienced accessibility developer: the biggest gain isn't just writing the fix — it's understanding context faster, locating where to change, and cutting research time down significantly.
Clear issue
- Manual
- 10 – 40 min
- With Resolver
- 5 – 15 min
- Time saved
- 50–70%
New project / low context
- Manual
- 30 min – 1.5 h
- With Resolver
- 10 – 35 min
- Time saved
- 50–70%
Parallel sessions multiply the impact
Because A11yResolver lets you work on 2, 3, or 4 issues simultaneously — across the same session or multiple sessions — the real productivity gain goes well beyond the per-issue numbers.
Getting started
Quick and simple to set up
-
Install the extension
Find A11yResolver in the VS Code Extension Marketplace and install it with one click.
Open in Marketplace -
Open the A11yResolver panel
Access the agent panel from the VS Code sidebar once installation is complete.
-
Add your OpenRouter API key
Connect your OpenRouter API key to enable AI-powered detection, refactoring, and validation.
-
Start fixing accessibility instantly
Run the agent on any component or file and get issues detected, fixed, and validated in seconds.
Agents
Choose the right mode for the job
-
Issues Resolver Fast
Best for everyday fixes, quick iteration, and lower cost. Handles the majority of common accessibility issues efficiently.
- Missing labels and alt text
- Non-semantic buttons and links
- Form field associations and validation messages
- Basic keyboard support and tab order
-
Issues Resolver Expert
Best for complex issues, deeper analysis, and stubborn problems. Uses more reasoning power to tackle edge cases.
- Modal dialogs and focus traps
- Dynamic ARIA states and live regions
- Complex React components and multi-step flows
- Custom widgets with composite keyboard patterns
Tip: Start with Fast. Switch to Expert when you need more reasoning power.
Notes
Requirements and practical details
-
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.
Compatibility
Works with your environment
- Windows x64
- macOS Apple Silicon
- macOS Intel
Support for additional platforms may be added in future releases.
Privacy & data
Your code stays on your machine
A11yResolver requires your own OpenRouter API key for AI features. Your key is stored securely in VS Code's secrets store — never sent to A11ySolutions servers.
-
API key stored in VS Code's secrets store
Your OpenRouter key never leaves your local environment. It is not transmitted to or stored by A11ySolutions.
-
What gets sent to OpenRouter
When you run a request, only the prompt and the code context needed for that specific task are sent to OpenRouter for processing. We do not include source file paths, API keys, or personal identifiers in any telemetry.
-
You stay in control
You decide whether to add an API key, which agent mode to use (Fast or Expert), and whether VS Code telemetry remains enabled. No account required to use the extension.
For details on how OpenRouter handles your data, see the OpenRouter Privacy Policy (opens in a new tab) .
Our accessibility expertise has contributed to projects for teams at…
FAQs
Frequently asked questions
Get started
Build accessibility into development from the start
A11yResolver helps teams detect, fix, and validate accessibility issues before code reaches production — so accessibility becomes part of the workflow, not a last-minute rework cycle.
Free during beta · Subscription pricing coming soon