No Bull. Make it xsbl.

No — and that distinction matters. Overlays inject JavaScript on your live site to paper over issues at runtime. They don't fix your code, they break screen readers, and courts have rejected them as compliance evidence. xsbl scans your rendered pages in a real browser, identifies the actual WCAG violations in your markup, and gives you code-level fixes (or opens a PR with them). Your source code gets better, not just the surface.

WCAG 2.2 AA is the baseline most organizations aim for — it covers essentials like color contrast (4.5:1 for normal text), alt text, keyboard navigation, and form labels. AAA is stricter: contrast jumps to 7:1, text must be resizable to 200%, and more. xsbl scans for both levels so you can decide how far to go. Most legal requirements reference AA, but hitting AAA on critical pages is a strong signal to procurement teams.

No. xsbl scans the publicly rendered version of your pages — the same HTML a browser sees. When you connect GitHub for PR creation, we read the relevant files only at the moment of generating a fix, and we don't persist your repository contents. Scan results (issue descriptions, selectors, fix suggestions) are stored in your account so you can track progress over time.

Connect your repo from the site detail page. When xsbl finds issues, it generates contextual code fixes based on your actual markup. You can create a PR for a single issue or bulk-fix up to 20 issues in one PR. The PR includes a description of what changed and why, mapped to specific WCAG criteria. Your team reviews and merges as normal.

Yes. All paid plans are month-to-month with no contracts. Cancel from your billing page and you'll keep access through the end of your current billing period. Your scan history and reports stay available on the free tier after downgrading.

When xsbl finds an issue — say a missing alt attribute or a low-contrast color — it doesn't just tell you what's wrong. It reads your actual element markup and generates a specific code snippet you can copy-paste to fix it. For example, instead of 'add an alt attribute,' you'd get the actual alt text written for your specific image in context.

Automated scanning catches roughly 30–50% of WCAG issues — the rest require manual testing (like checking tab order makes sense, or that custom widgets work with screen readers). xsbl covers the automated layer thoroughly and provides the evidence trail auditors want, but full compliance typically also involves manual review. We're upfront about that because the tools that promise 100% automated compliance are the ones getting fined.

Those are excellent tools — xsbl actually uses axe-core under the hood. The difference is workflow: xsbl wraps the scan engine in continuous monitoring, AI-generated fixes, GitHub PR creation, score tracking, and compliance reporting. Think of it as axe + CI/CD + project management for accessibility, rather than a one-off audit tab.