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.1 Keyboard AccessibleLevel AWCAG 2.0

2.1.1: Keyboard

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.

Why this matters

Users who cannot use a mouse — due to motor disabilities, blindness, or preference — rely on keyboard navigation. If interactive elements aren't keyboard accessible, these users are locked out of core functionality.

Common failures

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

Click handlers on <div> or <span> without keyboard support
Custom dropdowns that can't be navigated with arrow keys
Modal dialogs that don't trap focus
Drag-and-drop without keyboard alternatives
Hover-only tooltips with no keyboard trigger
Carousel controls that are mouse-only

How to fix

Use native interactive elements: <button>, <a>, <input>, <select>
If custom elements are necessary, add tabindex='0', role, and keyboard event handlers
Ensure all onClick handlers also work with Enter and Space keys
Implement keyboard support for custom widgets following WAI-ARIA patterns
Provide keyboard alternatives for drag-and-drop operations

Related axe-core rules

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

scrollable-region-focusable
nested-interactive

Check your site for 2.1.1 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.1.1: Keyboard (W3C)