The European Accessibility Act came into force in June 2025, and for a large class of businesses selling to EU consumers, "we'll get to accessibility later" stopped being an option. But most teams still treat accessibility the way they once treated security: a one-time audit before launch, a slide in a pitch deck, a line in the footer. Then it drifts. A new component ships with insufficient colour contrast, an icon-only button goes out without a label, a marketing page reuses a link style that screen readers can't distinguish. A11yProof started from a different premise: an accessibility posture is only useful if it is verifiable, current, and something you can act on. Every part of the product follows from that.
A11yProof is a WCAG 2.2 AA accessibility scanner, built on Laravel. You give it a URL, it loads the page in a real browser, runs it against the WCAG rule set, and returns a clear, severity-ranked report of exactly what fails and how to fix it — plus continuous monitoring and a public trust badge so the result stays honest over time.
Honesty First: We Sell Evidence, Not a Guarantee
The most important thing A11yProof does is refuse to lie to you. Automated tooling — any automated tooling, ours included — catches only roughly 30–40% of WCAG success criteria. The rest are judgement calls: is this alt text meaningful, does the reading order make sense, is this error message actually helpful? No scanner can answer those, and any product that sells you a "100% compliant" badge is selling a liability. So A11yProof never claims certification. It gives you evidence and monitoring: a documented, timestamped, repeatable record of what a machine can verify, with a plain statement of what it can't. That framing is a positioning rule, not a disclaimer — it runs through the copy, the reports, and the badge.
How the Scan Works
Under the hood, A11yProof drives headless Chrome through Spatie's Browsershot and injects axe-core — Deque's open-source accessibility engine, the same one behind most professional tooling — into the fully rendered page. Running against the real, JavaScript-executed DOM matters: modern sites build half their markup at runtime, and a scanner that only reads the initial HTML misses most of it. axe-core evaluates the page against the WCAG 2.0/2.1/2.2 A and AA rule set, and the JSON result — every violation, its impact level, the offending elements, and a link to remediation guidance — is parsed in PHP and rendered as a report. Each issue is ranked critical, serious, moderate, or minor, so you fix what matters first instead of drowning in a flat list.
One Language, All the Way Down
A11yProof follows the same engineering rule as the rest of the Talivio portfolio: it is a single Laravel monolith, with no separate services, runtimes, or deploys. The scanner, the web UI (a Livewire single-file component), the CLI, the badge — all PHP. The one exception is the headless-Chrome dependency Browsershot manages under the hood, and that is consumed as a package, never hand-written. This isn't dogma for its own sake: a small team owns and ships a codebase it fully understands far more reliably than a constellation of microservices in three languages. Boring, unified, and maintainable beats clever and fragmented.
Always-On: Monitoring and a Trust Badge
Because accessibility drifts, a single scan ages badly. A11yProof re-assesses registered domains on a schedule and records the result, so the picture stays current instead of rotting after launch. The visible payoff is a trust badge for your footer: a self-updating SVG seal that reflects the latest scan and links to a public status page showing the current state — issues found or none, broken down by severity, with a last-assessed date. It is a credible, independently-generated signal your visitors can check for themselves, and it degrades honestly: if the issues come back, so does the badge.
We Ran It on Ourselves First
Dogfooding isn't optional here. Before pointing A11yProof at anyone else, we ran it across talivio.com — every page, in all three languages — and it surfaced real problems: dozens of low-contrast text and button colours sitting just under the 4.5:1 threshold, a link that relied on colour alone to stand out, icon-only buttons with no accessible name, and a decorative marquee that was hidden from sight but still reachable by keyboard. We fixed every one and re-scanned until the pages came back clean. The talivio.com badge you see in the footer is the result of that pass — not a stock image, but a live attestation we earned. If a tool can't improve the site of the company that builds it, it has no business being sold.
Where It's Going
A11yProof is early and deliberately focused: do single-page WCAG scanning well, be honest about its limits, and make the result durable through monitoring and a public badge. From here the roadmap follows the same evidence-first thread — site-wide crawling so a whole domain can be assessed in one pass, a free single-page scan as an open front door, and downloadable audit reports and accessibility statements that give teams the paper trail the European Accessibility Act expects. You can try it now at a11yproof.talivio.com.
Why This Matters
The hard part of an accessibility product is not running the checks — axe-core does that well and openly. The hard part is honesty and durability: being clear about what a machine can and cannot verify, ranking findings so teams fix what counts, keeping the result current instead of frozen at launch, and making the whole thing something a business can point to and defend. A11yProof's answer is structural — a real-browser scan against the full WCAG rule set, severity-ranked and actionable, delivered by a single maintainable Laravel app, and kept honest by continuous monitoring and a public badge. It tells you where your site stands, and it keeps telling you.
