Find real WCAG issues on your site — free.
No injected scripts. No "AI overlay" sitting between your users and your site. AccessLens crawls your real pages and checks them against WCAG 2.1 AA — see how many issues you have in under a minute, then unlock every finding with exact before/after fixes in the full report.
Watch AccessLens run end-to-end.
A real screen recording of the scan widget below — a real URL goes in, a real crawl runs against the live production API, and real findings come back. Unedited.
Scan your own site — or app — right now.
Web scans run in under a minute (capped at 5 pages and 45 seconds so this stays free and fast for everyone). Android app scans run on a real device via Firebase Test Lab and take a few minutes. iOS isn't supported yet — real distributed IPAs are device-signed and can't run in a simulator without a paid device-farm integration we haven't built.
Figma's API only lets us see files shared with our account — share yours with rvv2005@gmail.com (view access is enough), then paste its URL below.
Two real compliance clocks are already running.
European Accessibility Act
Enforcement has been live since June 28, 2025 across all 27 member states, covering most digital products and services sold into the EU.
Penalties range €60K–€900K. First lawsuits have already been filed.
ADA Title II
DOJ requires WCAG 2.1 AA for state and local government sites and apps — April 2027 for jurisdictions over 50K population, April 2028 for smaller jurisdictions and special districts.
The pipeline is five real steps, not a black box.
A real headless browser crawls your live pages — not a cached snapshot, not a static export.
A deterministic rule engine checks accessible-name computation, contrast, form semantics, and heading structure against WCAG 2.1 AA. Every finding gets a confidence score, not a pass/fail flag.
A fix is generated — a markup diff, a CSS token swap, or AI-drafted copy, depending on what the rule actually needs.
If a fix touches more than one element on a page, it's routed to human review. It never auto-merges silently.
The fix opens as a normal pull request against your repo. Once merged, a re-scan confirms it actually landed.
Real scans, real targets, real findings.
web · scan → score → draft → gate → PR
github.com/abduznik/portfolio-dumper · real, unrelated public repo
Both a username input and an output textarea had no accessible name — nothing for a screen reader to announce (WCAG 1.3.1 / 4.1.2) — caught by a real scan against a real, unrelated public repo. One honest wrinkle, not glossed over: the automated diff-apply step correctly declined to guess here, since this site's rendered DOM doesn't byte-match its own hand-authored source (a known, documented limitation) — so this specific fix was applied by hand rather than auto-generated. Same end result: a real PR, verified afterward with a re-scan showing 0 remaining issues.
web
gohighlevel.com · 6 pages crawled
Every finding in that report is a real element from the live site, with the exact before/after markup diff — including one the engine correctly held back for human review rather than guessing at.
ios
github.com/okmoz/Habit (MIT) · 3 screens audited
Run against a real, unrelated open-source app — not our own demo — using Xcode's real accessibility audit wired into a UI test, the same integration shape a customer would add to their own CI. iOS has no black-box "scan any app" mode like Android, so this is the real, current shape of AccessLens's iOS product.
Nothing ships to your site unless you merge it.
AccessLens never runs anything at runtime on your site. There's no script tag, no DOM rewriting in the browser, no third-party layer between your users and your markup. Every fix is a diff, reviewed like any other pull request.
Confidence-scored — every finding carries a score based on how the fix was derived, not a flat true/false.
Blast-radius gated — a fix touching more than one element is routed to review, never auto-merged.
Diff-based, always — fixes are ordinary source changes your team already knows how to review.
Re-verified after merge — a fix isn't marked resolved until a re-scan confirms it actually landed.
Where AccessLens runs today.
Stated plainly — we'd rather tell you what's live than let a feature grid imply otherwise.
| Surface | Status | Detail |
|---|---|---|
| Web | Live | Full scan → score → PR pipeline running against real sites today. |
| iOS | In CI | XCTest-based accessibility audits gated in your own GitHub Actions — see the real proof above, run against a real open-source app. |
| Android | Live | Upload any APK above for a real scan on a real device via Firebase Test Lab — plus Espresso + Accessibility Test Framework gated in your own GitHub Actions. |
| Figma | Beta | Real WCAG 1.4.3 contrast checks against a live file via the scan widget above — share your file with us first (Figma's API only sees files granted access), no plugin install needed. |
Want more than a free scan?
Evaluating this for a team, need SSO/compliance details, or just want to talk through what a rollout would look like — leave a few details and we'll follow up directly.
Want to see what we'd find on your site?
Run the real scan above, or email us if you'd rather talk through the results with a person.