A: Great question — and honestly, a fair one. The "overlay debate" in the accessibility space is real, and we think about it a lot. Here's where WebAbility sits and why we believe we've built something genuinely different:

We're not a black box. Every fix we apply is visible in your dashboard — you can see exactly what changed, like "added aria-label='Search' to your search input" or "added skip navigation link." If you don't like a fix or think it conflicts with something, you can disable it individually. Full transparency, full control. No mystery JavaScript doing unknown things to your page.

You can hide the widget entirely — the fixes still work. You can set the widget button to hidden mode or trigger-only, and all the accessibility fixes stay active. The overlay is just the user-facing tool panel — it's completely separate from the remediation engine. Don't want a visible overlay? Don't use one. Your fixes keep running silently in the background.

We don't fight with screen readers. If a visitor is already using JAWS, NVDA, VoiceOver, or any browser accessibility tool, our widget detects that and backs off — it won't intercept keyboard shortcuts or compete with existing tools. The widget runs inside an isolated Shadow DOM, so it physically can't break your site's styles, scripts, or other extensions. The code-level fixes we apply (ARIA labels, landmark roles, skip navigation) actually make screen readers work better on your site — we're improving what assistive tech reads, not overriding it.

Zero impact on your site's performance. The initial script is ~67KB gzipped — smaller than most analytics trackers. The first time we analyze a page, the scanning waits until your page has fully loaded and the browser is idle — lazy-loaded, never competing with first paint. But here's the thing: once the fixes for your pages are calculated, they're cached. On every subsequent visitor load, those fixes apply in milliseconds — no re-scanning, no waiting, just instant remediation. Your Core Web Vitals are completely unaffected.

Our scanner goes way beyond typical overlay tools. Most accessibility overlays rely solely on axe-core or similar rule engines to detect issues. We use axe-core as a baseline, but our scanner also runs computer-vision analysis that mimics what a human auditor would catch — things like low color contrast that passes programmatic checks but fails visually, touch targets that technically meet minimum size but are unusable in context, focus indicators that exist but are invisible against the background, and layout issues that only show up when you actually look at the page. It's the difference between running an automated checklist and having someone actually use your site with their eyes and hands.

The overlay isn't our main value — the automated fixes are. Our scanner crawls your pages and applies real code-level remediation: missing ARIA labels, form input purposes, skip navigation, landmark roles, autocomplete attributes, empty link descriptions. These are the exact changes a developer would make by hand in your source code.

We help you actually remediate — not stay dependent on us. Beyond auto-fixes, we flag issues that need human review and show you exactly what to change in your own code. Applied (auto-fixed), advisory (here's what to change), needs review (requires a human call). The goal is native accessibility over time — we're a bridge, not a crutch.

No fake compliance claims. We don't slap a badge on your site and call it "ADA compliant." We show your real accessibility score, what's auto-fixed, what's advisory, and what still needs work. Honest reporting — you always know exactly where you stand.

To directly answer your concern: if someone already has a screen reader or browser extension, our fixes make those tools work better, not worse. We're fixing the actual HTML — proper labels, roles, autocomplete, skip links — so assistive tech can understand the page correctly. And if you want zero visible overlay, hide the button. Your fixes don't care.

We're not painting over problems. We're fixing the underlying page so it works for everyone — with or without our widget, with or without a screen reader.

Hope that clears things up! Happy to walk through your dashboard and show you the actual fixes on your sites anytime. You can contact us at [email protected] for any further questions or if you'd like a free onboarding session.