Cirv Guard vs accessiBe: Why an Overlay Widget Isn't a Compliance Strategy
ADA accessibility lawsuits against websites hit a record high in 2023, with over 4,600 federal cases filed. The number climbs every year. That pressure has made accessibility a real business concern for WordPress site owners, and it's created a market for tools that promise to solve the problem quickly.
accessiBe is the most heavily marketed of those tools. It promises WCAG compliance through an AI-powered overlay widget that installs in minutes. Cirv Guard takes a different approach: it scans your rendered HTML, identifies specific accessibility violations, and gives you a clear picture of what needs fixing.
These are fundamentally different products solving the problem in fundamentally different ways. Understanding that difference matters before you spend money or stake your legal compliance on either one.
What accessiBe Actually Does
accessiBe is an overlay widget. You install a JavaScript snippet and it adds a floating button to your site. When a visitor clicks it, a sidebar opens with options to increase font size, change contrast, pause animations, and so on.
The AI component attempts to automatically modify how assistive technologies like screen readers interpret your pages — adding ARIA labels, adjusting focus order, and filling in missing alt text — without changing your actual HTML. The idea is that the overlay intercepts and corrects the experience for users with disabilities at the frontend layer.
Pricing starts at $49/month for a single domain, scaling to $149/month for larger sites. There's no free tier.
The Core Problem with Overlays
The accessibility community has written extensively about why overlays don't work as advertised. The Overlay Fact Sheet has been signed by hundreds of accessibility professionals, and the objections are substantive:
- Overlays intercept assistive technology but don't fix the underlying HTML. A screen reader accessing your page without JavaScript gets none of the overlay's modifications.
- Automated AI cannot reliably determine the correct alt text for every image, the right heading structure for every page, or the proper ARIA roles for every custom widget. Context matters, and AI gets context wrong.
- Several blind users and accessibility advocates have published accounts of overlays making their experience worse — interfering with their preferred screen reader settings.
- Legal protection from overlays is not guaranteed. Multiple lawsuits have proceeded against sites using accessiBe and similar products. The presence of an overlay has not consistently served as a legal defense.
None of this means accessiBe is worthless. The widget features — font size controls, contrast toggles — are legitimate usability tools. The problem is the framing: it's sold as a compliance solution, and compliance requires fixing your actual content, not applying a layer on top of it.
What Cirv Guard Does
Cirv Guard is an accessibility scanner. It has no frontend component — there's no widget, no floating button, nothing visible to your visitors. It runs inside the WordPress admin and scans the rendered HTML of your pages.
The free version checks five categories of WCAG 2.1 AA criteria:
- Alt text — images missing alt attributes or using placeholder text like "image001.jpg"
- Heading structure — skipped heading levels (h1 to h3 with no h2), multiple h1s, missing headings
- Color contrast — foreground/background combinations that fail the 4.5:1 ratio using the WCAG luminance formula
- Form labels — inputs without associated label elements or aria-label attributes
- Link accessibility — "click here" and "read more" links without descriptive context
Because it scans rendered HTML rather than post content, it catches issues introduced by themes, page builders, and third-party plugins — not just content you wrote yourself.
The Pro version ($12/month or $99/year) adds full WCAG 2.1 AA audit coverage, automated scan scheduling, PDF compliance reports you can share with clients or stakeholders, and remediation suggestions that tell you exactly what HTML change will fix each issue.
Head-to-Head Comparison
| Feature | accessiBe | Cirv Guard (Free) | Cirv Guard Pro |
|---|---|---|---|
| Price | $49–$149/month | Free | $12/month or $99/year |
| Free on WordPress.org | No | Yes | — |
| Scans actual HTML | No (overlay) | Yes | Yes |
| Frontend widget added | Yes | No | No |
| Alt text checking | AI-generated (automated) | Flags missing alt text | Full audit + suggestions |
| Heading structure audit | AI-adjusted (overlay) | Yes | Yes |
| Color contrast analysis | User toggle (approx.) | Yes (WCAG formula) | Yes |
| Form label validation | AI-adjusted (overlay) | Yes | Yes |
| PDF compliance reports | No | No | Yes |
| Remediation guidance | None (auto-applied) | Issue list | Specific fix suggestions |
| Works without JavaScript | No | Yes (admin-only) | Yes |
| Affects page performance | Yes (JS payload) | No | No |
| Works with page builders | Varies | Yes (scans rendered HTML) | Yes |
| Automated scan schedule | Continuous | No | Yes |
The Compliance Question
The ADA and Section 508 require that your website's content is accessible. Courts have generally applied the WCAG 2.1 AA standard as the benchmark. What WCAG measures is the actual experience of users with disabilities — not what an overlay claims to do, but what they actually encounter.
An overlay that auto-generates alt text for images gets some images right and others wrong. A legally defensible approach requires that every image on your site has accurate, descriptive alt text. The only way to ensure that is to audit your content, identify what's missing or incorrect, and fix it.
Cirv Guard gives you a list of specific issues to fix. That list is the starting point for actual remediation. Once you fix the issues it identifies, your HTML is genuinely more accessible — for every user, with or without assistive technology, with or without JavaScript.
No scanner, including Cirv Guard, catches 100% of accessibility issues. Automated tools can't evaluate cognitive accessibility, check that captions are accurate, or assess whether a navigation structure makes sense. But they catch the most common, most consistently cited violations — the ones that appear in the majority of ADA lawsuits.
Performance Impact
accessiBe loads a JavaScript widget on every page of your site. The script itself is several hundred kilobytes, and it must initialize on each page load to apply its AI modifications. For sites optimizing Core Web Vitals — particularly Largest Contentful Paint and Total Blocking Time — this is a measurable cost.
Cirv Guard has zero frontend impact. It runs entirely in the WordPress admin. Your visitors never load a single byte from it. Your page speed scores are unaffected.
When accessiBe Makes Sense
There's one scenario where an overlay adds genuine value: an enterprise site with thousands of pages that needs quick improvements while a longer remediation project runs in parallel. The widget's user controls — font sizing, contrast, motion reduction — are features that some users find useful regardless of compliance status.
If you have the budget and you're treating accessiBe as a temporary measure while you do the harder work of fixing your HTML, it's not a harmful choice. The problem is treating it as a final solution.
The Bottom Line
If you're choosing between spending $49/month on a frontend overlay and spending time fixing the actual issues in your HTML, fix the HTML. That's what creates real accessibility, and it's what holds up when a plaintiff's attorney runs a screen reader through your site.
Cirv Guard's free version gives you a starting point: a scan of your site that flags the most common WCAG violations, tells you exactly where they are, and lets you start fixing them. No monthly subscription required to find out where you stand.
Pro upgrade ($99/year) adds full WCAG 2.1 AA coverage, scheduled scans to catch regressions when you publish new content, and PDF reports — useful if you're managing accessibility for clients or need documentation for compliance purposes.