Closed alpha · Automated UX and visual QA
Vizlint reviews every page of your site at the breakpoints you choose. Each finding points to the element, the measurement, the screenshot and a suggested fix. No baseline, no test code.
01 / Who it’s for
You built fast, with Cursor, Claude Code, v0 or Lovable. Before real people arrive, Vizlint checks what a careful reviewer would: text nobody can read, buttons too small to tap, copy that still says lorem ipsum.
02 / How it works
Use a public or staging address. For a local build, open a tunnel. Pick the widths you care about and the browsers to capture.
It follows the links on your page, up to 20 pages, and captures each one at every width. A scan finishes inside 10 minutes or keeps its partial results.
Each finding names the element, shows the measured value next to the required one, and suggests a fix. Copy the list straight into your coding agent.
03 / The checks others skip
Most QA tools look at pixels and code. Vizlint also reads your words, on the first scan, with nothing to compare against.
“Unlock seamless experiences that elevate every interaction.”
Suggested fix
This text has unusually high buzzword density. Consider rewriting with more specific, authentic language.
04 / What it checks
Every check runs on every page, at every width you choose, in each browser you pick.
Captured in Chromium, WebKit and Firefox. Not real devices.
Automated checks, not an accessibility certification.
05 / The report
The report shows the score, each page, and every finding with its evidence. People you send it to don’t need an account. The site and findings in this sample are illustrative.
Open the sample report (full-size image, opens in a new tab)
“I’ve worked as a designer reviewing developer implementations and as an engineer shipping UI without a repeatable quality check. AI increased the amount of interface code, but the review process stayed manual. I built Vizlint to make those checks repeatable.”
Fábio AlencarFounder · Designer and UX engineer
07 / Questions
No. Vizlint runs automated checks, including contrast and alt text, but it doesn’t certify a site against WCAG. Use it to catch problems early, then review the rest by hand.
Not directly. Vizlint needs a public or staging URL. For a local build, open a tunnel and paste the tunnel’s address.
They stay with the scan in your account until you delete the scan.
Nothing during the closed alpha. Pricing comes later, and we’ll tell you before anything changes.
No. Every finding comes from a fixed rule you can read, with the measured value next to the required one.
Closed alpha
Vizlint is opening to a small group at a time. Until requests open here, the sample report shows what a scan finds.
See the sample report