I build open source accessibility testing frameworks and developer tools that integrate seamlessly into existing workflows. From component-level testing to browser extensions, these projects focus on making accessibility testing effortless and developer experience exceptional.
Currently experimenting with bringing real-time accessibility feedback to Storybook. The idea is simple—developers already live in Storybook for component development, so why not catch accessibility issues right there? I'm building this with a freemium model (free npm package, paid cloud features) inspired by how Chromatic does it. Still in the prototyping phase, but the monorepo is set up and I'm integrating the same observer patterns that made CAT successful.
When you're building tools for 10,000+ developers, you learn quickly that if it's not easy, it won't get used. I led the effort to bake accessibility testing directly into Fidelity's CI/CD pipelines and built a browser-based monitoring tool that gives developers instant feedback. The best part? Watching teams across different business units adopt the component patterns we created. Turns out making accessibility easy is the key to making it universal.
I built this because I was tired of accessibility testing being bolted on as an afterthought. CAT runs continuously during your existing Playwright, Cypress, or WebdriverIO tests—no changes to your test code required. It watches for UI changes using observers and catches accessibility issues in real-time. The DOM fingerprinting system I added keeps test reports clean by filtering out duplicate violations. It's the testing tool I wish I'd had years ago.
Over the years, I've built a collection of accessibility testing integrations for the tools developers actually use. Test wrappers for Playwright and Cypress, a browser extension (WXT + Vue) for real-time feedback while you code, component linters for Vue, Angular, and Lit. Each one solves a specific pain point I've seen teams struggle with. It's all about meeting developers where they already are instead of forcing them to adopt new workflows.