{"slug": "how-i-cut-accessibility-remediation-time-by-70-without-leaving-vs-code", "title": "How I cut accessibility remediation time by 70% without leaving VS Code", "summary": "A developer built A11yResolver, a VS Code extension that uses an AI agent to detect and fix WCAG accessibility issues directly within the editor. The tool offers two modes—Fast for common issues and Expert for complex cases—and validates fixes through real browser interaction, reducing remediation time by 50–70% in tracked projects.", "body_md": "**The problem**\n\nEvery 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.\n\nIt wasn't hard work. It was repetitive work. And it was eating hours every sprint.\n\n**What we built**\n\nA11yResolver is a VS Code extension that brings that entire loop inside the editor.\n\nIt 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.\n\n**The two modes**\n\n**Issues Resolver Fast** — the everyday one. Missing labels, non-semantic buttons, form field associations, basic keyboard support. Quick iteration, lower cost.\n\n**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.\n\nStart with Fast. Switch to Expert when it can't fully resolve something.\n\n**What surprised me**\n\nIt 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.\n\n**Setup**\n\nYour own API key means you pay the token cost directly, no markup, no subscription for the AI part. Free during beta.\n\n**Results**\n\nIn 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.\n\n**Try it**\n\n→ [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=A11YSolutions.a11y-resolver-vscode-chat)\n\n→ [Full demo](https://app.trupeer.ai/view/2meqGnCDI/a-11-y-resolver-user-guide)\n\n→ [Product page](https://www.a11ysolutions.com/resolver)\n\nQuestions welcome in the comments.", "url": "https://wpnews.pro/news/how-i-cut-accessibility-remediation-time-by-70-without-leaving-vs-code", "canonical_source": "https://dev.to/a11ysolutions/how-i-cut-accessibility-remediation-time-by-70-without-leaving-vs-code-igi", "published_at": "2026-06-18 14:24:38+00:00", "updated_at": "2026-06-18 14:51:39.487788+00:00", "lang": "en", "topics": ["developer-tools", "artificial-intelligence", "ai-agents", "large-language-models"], "entities": ["A11yResolver", "VS Code", "WCAG", "A11YSolutions"], "alternates": {"html": "https://wpnews.pro/news/how-i-cut-accessibility-remediation-time-by-70-without-leaving-vs-code", "markdown": "https://wpnews.pro/news/how-i-cut-accessibility-remediation-time-by-70-without-leaving-vs-code.md", "text": "https://wpnews.pro/news/how-i-cut-accessibility-remediation-time-by-70-without-leaving-vs-code.txt", "jsonld": "https://wpnews.pro/news/how-i-cut-accessibility-remediation-time-by-70-without-leaving-vs-code.jsonld"}}