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.

All WCAG criteria

Operable2.4 NavigableLevel AAWCAG 2.0

2.4.7: Focus Visible

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

Why this matters

Sighted keyboard users need to see where focus is. Without a visible focus indicator, they can't tell which element is active, making the interface unusable for keyboard navigation.

Common failures

These are the most frequent ways this criterion is violated in real-world websites:

CSS outline:none without a replacement focus style
Focus styles that are nearly invisible (thin dotted outline in low contrast)
Focus styles removed on buttons or links for aesthetic reasons
Custom focus styles that don't provide sufficient contrast

How to fix

Never remove outline without providing a visible alternative
Use :focus-visible for styles that only appear during keyboard navigation
Ensure focus indicators have at least 3:1 contrast and are clearly visible
Example: :focus-visible { outline: 2px solid #4338f0; outline-offset: 2px; }

Related axe-core rules

xsbl uses axe-core to automatically detect violations of this criterion. The following rules are checked:

focus-order-semantics

Check your site for 2.4.7 violations

xsbl scans your rendered pages in a real browser and finds violations of this criterion automatically.

Scan your site free

Official reference: Understanding WCAG 2.4.7: Focus Visible (W3C)