The problem Every time I found an accessibility issue in a PR review, the same thing happened: tab...
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.
The pattern that pushed me to build this: I'd fix an accessibility issue, ship, and a few deploys...
Automated accessibility testing usually means one thing: point a scanner at the page, let it check...
For the Finish Up-A-Thon, I worked on an AI-powered VS Code extension focused on improving developer...
Accessibility audits usually happen late. A tool runs on the deployed site, flags a dozen...
I've been building with Angular for ten years, and in that time I've watched the same thing happen on...
Every time I do a website audit I run into the same problem. The checklist is open in one tab, the...
