xsbl is an AI-powered web accessibility scanner that checks your website against WCAG 2.2 AA and AAA criteria. It scans your rendered pages in a real browser, identifies violations like missing alt text, contrast failures, broken ARIA, and keyboard traps, and generates specific code fix suggestions for your actual markup.

How is xsbl different from accessibility overlays?

Unlike overlays that inject JavaScript and only detect about 30% of WCAG issues, xsbl scans your actual rendered DOM in a real Chromium browser. It provides real code fixes instead of cosmetic patches, works with screen readers rather than against them, and produces exportable compliance evidence accepted by courts and auditors.

Does xsbl support WCAG 2.2?

Yes. xsbl covers 90+ rules across WCAG 2.2 AA and AAA criteria, including contrast, alt text, ARIA, keyboard navigation, forms, headings, landmarks, and more. Each issue is mapped to the specific WCAG success criterion it violates.

Can xsbl create GitHub pull requests with accessibility fixes?

Yes. Connect your GitHub repository and xsbl can generate pull requests with AI-suggested code fixes for accessibility issues. You can fix individual issues or use bulk fix to address multiple issues in a single PR.

How much does xsbl cost?

xsbl offers a free tier with 1 site and 3 scans per month. Paid plans start at $19/month for Starter, $69/month for Pro with unlimited sites and 100 scans, and $249/month for Agency with white-label reports, VPAT generation, and dedicated support.

IndustryFebruary 22, 20268 min read

Why Accessibility Overlays Don't Work (And What to Do Instead)

The FTC fined the market leader $1M. Over 600 experts oppose them. Here's what actually works.

Accessibility overlays — JavaScript widgets sold by companies like accessiBe, UserWay, and AudioEye — promise to make your website compliant with a single line of code. It sounds too good to be true. That's because it is.

What overlays actually do

Overlays inject a JavaScript widget into your page that attempts to patch accessibility issues at runtime. They add toolbar buttons for things like font size adjustment, contrast toggles, and reading modes. The pitch is compelling: drop in one script tag, and your website becomes WCAG compliant overnight.

The reality is different. Overlays don't modify your source code. They paper over problems with runtime JavaScript that frequently conflicts with assistive technologies. Screen reader users report that overlays often make sites harder to use, not easier. The National Federation of the Blind has explicitly called out overlay vendors for misleading claims.

The legal reality

In 2024, the FTC fined accessiBe $1 million for deceptive marketing practices. Over 800 businesses using overlay widgets were sued for ADA violations in 2023 and 2024 — having an overlay installed didn't protect them. Courts have consistently ruled that overlays are not evidence of accessibility compliance.

The Overlay Fact Sheet, signed by over 600 accessibility professionals from organizations including Google, Apple, and Microsoft, states plainly: overlay solutions do not meet the legal requirements for accessibility.

What actually works

Real accessibility requires fixing your actual source code. There's no shortcut. The good news is that most issues are simple — adding alt text to images, fixing color contrast values, using semantic HTML elements instead of divs, adding proper form labels.

Tools like xsbl scan your codebase, identify the specific issues, and can automatically generate code fixes as pull requests. Instead of masking the problem with a runtime widget, you're improving your actual code. The fixes are permanent, they work with assistive technology instead of against it, and they hold up in court.

Ready to fix your accessibility issues?

Scan your site free. Get AI-powered fixes as pull requests.

Start scanning free