1
1 Comment

No more vague visual QA slack messages...

I've been a designer for 15 years. The same problem kept showing up on every project: designs look perfect in Figma, then something drifts in the build. Spacing is off, colors don't match, an accessibility issue slips through.

The usual fix? Open Figma in one tab, the staging site in another, squint back and forth, then write up a ticket that says "the padding looks wrong on the hero." The developer asks which padding. You screenshot it. They screenshot theirs. Three days of back-and-forth for a 2-minute fix.

So I built OverlayQA.

It's a Chrome extension (in-product capture coming soon) that lets you compare your Figma designs directly against the live page, run AI-powered accessibility audits, check design system token consistency, and export everything to Jira, Linear, Notion, or Slack and more with full context (CSS values, screenshots, viewport, selectors) so there's nothing to guess.

The core loop is: capture what's wrong, get AI analysis, export with full context. No more "can you send me a screenshot of what you mean."

We're live on the Chrome Web Store. Would love feedback from anyone who's felt this pain.

posted toAvatar for product OverlayQA
OverlayQA
  1. 1

    happy to answer questions or give a walkthrough if anyones interested!