The problem
Every time I found an accessibility issue in a PR review, the same thing happened: tab out to the WCAG docs, figure out the right fix, come back to the code, apply it, re-verify. For every single issue.
It wasn't hard work. It was repetitive work. And it was eating hours every sprint.
What we built
A11yResolver is a VS Code extension that brings that entire loop inside the editor.
It runs as an AI agent. It flags WCAG issues in context, not as static linting, but understanding the component and what it produces. Then it suggests a standards-based fix you can review as a diff and apply with one click.
The two modes
Issues Resolver Fast — the everyday one. Missing labels, non-semantic buttons, form field associations, basic keyboard support. Quick iteration, lower cost.
Issues Resolver Expert — for the harder stuff. Focus traps, dynamic ARIA states, live regions, complex multi-step flows. More reasoning power for the edge cases.
Start with Fast. Switch to Expert when it can't fully resolve something.
What surprised me
It validates fixes through real browser interaction, not just code analysis. It actually simulates keyboard navigation and checks that focus management works correctly. That's the part most tools skip.
Setup
Your own API key means you pay the token cost directly, no markup, no subscription for the AI part. Free during beta.
Results
In the projects where we've tracked it: 50–70% less time on repetitive remediation. The gain isn't speed, it's not doing the work twice.
Try it
→ [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=A11YSolutions.a11y-resolver-vscode-chat)
→ [Full demo](https://app.trupeer.ai/view/2meqGnCDI/a-11-y-resolver-user-guide)
→ [Product page](https://www.a11ysolutions.com/resolver)
Questions welcome in the comments.