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

Perceivable1.3 AdaptableLevel AWCAG 2.0

1.3.1: Info and Relationships

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Why this matters

When headings, lists, tables, and form labels are only visually styled but not semantically marked up, assistive technologies cannot convey the structure to users. A sighted user sees a bold heading; a screen reader user hears undifferentiated text.

Common failures

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

Using <b> or font-size for headings instead of <h1>-<h6>
Form inputs without associated <label> elements
Data tables without <th> headers
Lists built with <div> and dashes instead of <ul>/<ol>
Required fields indicated only by color
Fieldsets without legends for grouped controls

How to fix

Use semantic HTML: <h1>-<h6> for headings, <ul>/<ol> for lists, <table> with <th> for data
Associate labels with inputs using for/id or wrapping: <label for='email'>Email</label><input id='email'>
Use <fieldset> and <legend> for related form controls
Mark required fields with aria-required='true' in addition to visual indicators

Related axe-core rules

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

label
form-field-multiple-labels
input-button-name
select-name
empty-heading
p-as-heading
definition-list
dlitem
list
listitem
td-headers-attr
th-has-data-cells
table-fake-caption

Check your site for 1.3.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 1.3.1: Info and Relationships (W3C)