A multi-tenant SaaS product for accessibility compliance. Scan any page for WCAG issues in a real browser (axecore, WCAG 2.0–2.2) — then Webscan drafts the code fix, you approve it, it opens a pull request, and a rescan verifies the issue is actually gone. Free instat check, no signup.
Hi Product Hunt 👋 I'm Archebold, founder of Inclusive App Craft in Accra, Ghana — and I'm a screen reader user myself. Webscan comes straight out of my own daily frustrations.
The first spark: my university's LMS put an autofocus on a chatroom message field — but site-wide. So every time I opened a course page, or even the tools menu, my screen reader was yanked into "type your chat message," and the menu disappeared. One misplaced attribute turned the whole site into a maze. I wanted a scanner that catches issues like that — the ones living in JavaScript-heavy, interactive, logged-in flows, not just static HTML. That's why Webscan has authenticated scanning, user journeys, and agentic exploration.
The second: developers keep telling me WCAG is too long to read. During my National Service at the University of Ghana's IT Directorate, I was handed an accessibility report and asked, "could you actually fix the issues with this?" I couldn't — it wasn't enough to guide a real fix. A report isn't a fix. So Webscan doesn't stop at findings: it drafts the actual code fix, you approve it, it opens a pull request, and a re-scan verifies the issue is truly gone.
The third: most tools only scan public, static pages. But so many barriers live behind a login — so Webscan scans there too.
Every feature has a reason like this. The goal is simple: make accessibility something teams can actually finish, so people who rely on assistive technology aren't left struggling to navigate the web.
Free instant check, no signup — try it on any URL. I'd genuinely love your feedback. 🙏
Hi Product Hunt 👋 I'm Archebold, founder of Inclusive App Craft in Accra, Ghana — and I'm a screen reader user myself. Webscan comes straight out of my own daily frustrations.
The first spark: my university's LMS put an autofocus on a chatroom message field — but site-wide. So every time I opened a course page, or even the tools menu, my screen reader was yanked into "type your chat message," and the menu disappeared. One misplaced attribute turned the whole site into a maze. I wanted a scanner that catches issues like that — the ones living in JavaScript-heavy, interactive, logged-in flows, not just static HTML. That's why Webscan has authenticated scanning, user journeys, and agentic exploration.
The second: developers keep telling me WCAG is too long to read. During my National Service at the University of Ghana's IT Directorate, I was handed an accessibility report and asked, "could you actually fix the issues with this?" I couldn't — it wasn't enough to guide a real fix. A report isn't a fix. So Webscan doesn't stop at findings: it drafts the actual code fix, you approve it, it opens a pull request, and a re-scan verifies the issue is truly gone.
The third: most tools only scan public, static pages. But so many barriers live behind a login — so Webscan scans there too.
Every feature has a reason like this. The goal is simple: make accessibility something teams can actually finish, so people who rely on assistive technology aren't left struggling to navigate the web.
Free instant check, no signup — try it on any URL. I'd genuinely love your feedback. 🙏