Pillar Guide
Design QA is the practice of systematically reviewing a built product against its original design specifications to identify and resolve visual discrepancies before users encounter them.
Visual quality directly impacts business outcomes. 94% of first impressions are design-related, and users form opinions in approximately 50 milliseconds. Fixing bugs post-launch costs 5-10x more than catching them during QA.
The design source of truth should be a single, versioned Figma file that reflects the latest approved designs.
Design QA should happen on a staging environment before the code ships to real users.
Systematically compare the staging build against the design spec using overlay tools or side-by-side comparison.
Include CSS selectors, computed values, screenshots, and Figma frame links in every bug report.
Re-verify fixes on staging and add visual regression tests for critical screens.
| Aspect | Design QA | Traditional QA |
|---|---|---|
| Focus | Visual fidelity | Functional correctness |
| Tools | Figma overlay, DevTools, visual diff | Selenium, Cypress, Playwright |
| Who | Designers, front-end devs | QA engineers, SDETs |
| Timing | Before merge on staging | Throughout development |
OverlayQA is a browser extension for the design QA workflow. Overlay Figma designs on staging builds, click any element to capture CSS properties and screenshots, and export structured issues to Jira or Linear.