Automatic issue detection and refactoring
Automatically detects and fixes accessibility issues such as missing labels, low contrast, keyboard traps, and more by intelligently refactoring components.
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.
What it does
Detect, fix, and validate accessibility issues where code gets written
A11yResolver is built to help developers solve accessibility issues directly inside their workflow instead of discovering them later during audits, QA, or post-launch remediation.
Real browser validation
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.
Conversational code remediation
Refactors code through a conversational agent — describe what you need or let it propose and apply changes.
Session memory
Remembers your session so you can continue exactly where you left off.
1-command example
Fix accessibility issues automatically with a single command
Changes applied
- Added proper accessible labels and alt text
- Replaced non-semantic elements with correct structure
- Enabled full keyboard navigation
- Improved ARIA attributes for screen readers
WCAG conformance AA Compliant ✓
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 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.
-
Issues Resolver Expert
Best for complex issues, deeper analysis, and stubborn problems. Uses more reasoning power to tackle edge cases.
Tip: Start with Fast. Switch to Expert when you need more reasoning power.
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
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.
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.
No commitment required · WCAG 2.2 AA