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

Understandable3.1 ReadableLevel AWCAG 2.0

3.1.1: Language of Page

The default human language of each Web page can be programmatically determined.

Why this matters

Screen readers use the language attribute to select the correct pronunciation engine. Without it, an English screen reader might try to pronounce French text with English phonetics, making it incomprehensible.

Common failures

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

Missing lang attribute on <html> element
Incorrect language code (e.g. lang='english' instead of lang='en')
Language not matching the actual page content

How to fix

Add the lang attribute to the html element: <html lang='en'>
Use valid BCP 47 language tags: en, es, fr, de, ja, zh, etc.
For pages with mixed languages, set the primary language on <html> and use lang on specific elements

Related axe-core rules

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

html-has-lang
html-lang-valid
html-xml-lang-mismatch

Check your site for 3.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 3.1.1: Language of Page (W3C)