Visual QA for design drift
Almost every page has UI drift. A minor spacing miss, a wrong color, an accessibility issue. As time goes by, design debt grows. That is where Scan UI fits.
How it works
- Open staging or production in Chrome and run Scan UI.
- Check the page against itself, against Figma tokens, or against a DESIGN.md.
- Preview a finding, apply the fix on that URL, share it, or send Changes to an agent.
What Scan UI finds
- Wrong or leftover colors and type.
- Spacing and layout misses, including borders and effects.
- Spelling on the live page.
- Accessibility flags and an accessibility score out of 100.
Three ways to scan
- The page against itself. Consistency on the URL, no design file required.
- Figma token baseline. Live CSS vs variables you pasted from Overview.
- DESIGN.md. Check the page against a spec you upload or paste.
Findings are deterministic first. Optional AI insight can sit on top. Preview and apply from the same cards, or copy a scan prompt for a coding agent.
Frequently asked questions
What is visual QA in inspecta?
Checking the live UI for design drift and accessibility, then applying the fix on that page. Scan UI is the scan. It is not a CI pixel diff.
What is Scan UI?
The visual QA scan on a live page. It finds design drift and accessibility issues as design debt grows: leftover colors, fonts, spacing, layout, spelling, borders, effects, and an accessibility score.
Does every page have drift?
Almost. A miss can be small, a spacing gap or a wrong color. After a few sprints those pile up. Scan UI is for that debt. Page overview is for seeing the full picture of what the page uses.
Does inspecta check accessibility?
Yes. You get accessibility flags and an accessibility score out of 100 on the same scan. Copy an accessibility prompt for a coding agent if you want the fix in the repo.
Can I do this without a Figma file?
Yes. Check the live page against itself. Add Figma tokens or a DESIGN.md when you have a spec. Comparing a frame to the live site is a separate flow.
Is this the same as comparing Figma to production?
No. Scan UI finds drift and accessibility on the URL you have open. Compare Figma to your live site when the file is the source of truth.
Do visitors see the fixes?
No. Edits stay in your browser until you share a link or send CSS to a developer or to Cursor.