Loupe runs an instant WCAG 2.1 & 2.2 audit on any page (powered by axe-core), shows every issue in context with plain-English fixes, and exports a white-label PDF report with your own logo. Crawl up to 8 pages at once. Everything scans locally, so page content never leaves your browser. Free for scanning; Pro ($19/mo) adds branded reports, full-site crawl, and saved projects. Built for freelancers and agencies who need to hand clients a report they'll understand.
No reviews yetBe the first to leave a review for Loupe
Maker
📌
Hey Product Hunt 👋
I'm Róbert, and I build small web tools from Iceland. Loupe is one of them, part of my studio Lucency.
I built it because accessibility checking always felt half-finished to me. The free tools like axe and WAVE are genuinely good at finding issues. But if you do client work, finding them is only half the job. You still have to turn a wall of technical findings into something a client will read, understand, and actually pay for. That report part was always manual and a bit miserable.
So Loupe tries to cover the whole thing. You click the icon and it runs a WCAG audit on the page (axe-core underneath, so the detection is solid). Every issue is explained in plain English with how to fix it. Then you can export a clean PDF report with your own logo on it, or crawl a whole site into one combined report.
It all runs locally, so the page content never leaves your browser. Scanning is free for good. Pro is $19/mo or $190/yr and adds the branded reports, the full-site crawl, and saved client projects.
One thing I want to be upfront about: no automated tool catches everything, including this one. I built it as a fast first pass, not a replacement for a human checking the things only a human can. I'd rather say that than oversell it.
I'd really love feedback, especially from other freelancers and agencies. What would make a report genuinely useful to hand a client?
Report
The local-only scanning is a nice touch for client work, and the plain-English fixes actually read like something I'd send to a non-developer without rewriting them.
Report
Maker
@tansu750955 Thanks, really glad those two landed, because they’re the parts I sweated over most. The local scanning was non-negotiable for me since client pages are often staging or behind a login and I didn’t want any of that leaving the browser. And the plain-English bit was the whole reason I built this instead of just using axe raw, that gap between “here’s a rule ID” and “here’s what I tell the client” was the annoying manual step.
Since you clocked the report angle: if you do client work, what would make a report actually useful to hand someone? That’s the thing I most want to get right.
The local-only scanning is a nice touch for client work, and the plain-English fixes actually read like something I'd send to a non-developer without rewriting them.
@tansu750955 Thanks, really glad those two landed, because they’re the parts I sweated over most. The local scanning was non-negotiable for me since client pages are often staging or behind a login and I didn’t want any of that leaving the browser. And the plain-English bit was the whole reason I built this instead of just using axe raw, that gap between “here’s a rule ID” and “here’s what I tell the client” was the annoying manual step.
Since you clocked the report angle: if you do client work, what would make a report actually useful to hand someone? That’s the thing I most want to get right.