Skip to content
Kerb — home

Accessibility checks for small online stores

Find out what’s stopping people shopping on your store.

Paste your store address. Kerb opens your pages the way a screen reader, a keyboard and voice control do — then tells you what breaks, the part of the page it breaks on, who it stops, and how to fix it.

Plain English for you, developer detail in an appendix for whoever maintains your site. No overlay widget that papers over the problem — the actual change to make.

The score is free and takes about 30 seconds. No account, no card.

Free
Your score, in 30 seconds
€49 once
The full report, plus the first month of monitoring
€29 a month
Monthly re-scans after that

The full report

€49 once — the whole list, not a teaser

One payment, one store. You get every failure the scan finds, ordered by what costs you sales, and the first month of monitoring is already running.

  • Every problem, located

    Each failure is named with the page it’s on, the exact element, and the rule it breaks, so nobody has to go hunting.

  • Who it blocks, in plain words

    Not “insufficient contrast”: “the sale price is too faint against the card, so people with low vision see a smudge instead of a number.”

  • The fix, ready to hand over

    The change to make in your theme, with a before-and-after snippet. Your developer can start without a meeting.

  • Ordered by what loses you sales

    Anything that stops a shopper searching, choosing a size or paying comes first. Cosmetic problems come last.

  • The pages that matter, scanned

    Home, a collection page, a product page, cart, search results, and contact or legal.

  • A PDF you can forward

    Plain English first, developer appendix behind it. Send it to your developer or your agency, or keep it on file.

Scan your storeScan first, pay only if the report is worth it.

A real scan, anonymised

What you actually get back

Three findings from a real scan of a mid-sized apparel store, with the store’s name and addresses removed. Same scan you’ll run, same words you’ll read.

Anonymised apparel store

4 pages audited · 37 failing elements · 112 checks passed

41out of 100

  1. Critical

    Sale prices can’t be read by people with low vision

    On every product card, the crossed-out original price and the red sale price sit too close in colour to the card background. Someone with low vision — or anyone shopping on a phone in daylight — sees a faint smudge instead of a number, and can’t tell whether they’re saving €30 or €3.

    The fix: Darken the sale price, or lighten the card behind it, until the contrast passes. One colour value in your theme.

    For your developer
    Criterion
    WCAG 1.4.3 Contrast (Minimum)
    Rule
    color-contrast · 18 elements
    Element
    <span class="price--sale">€59.00</span>
    What it found
    Measured 2.9:1 against the #F7F7F7 card background. Text this size needs at least 4.5:1.
  2. Serious

    The search box has no name

    The search field at the top of every page is an empty box to a screen reader. It announces “edit text” with no clue that it searches the store. A screen reader user who wants to find one product has to guess that this is the way — most give up and leave.

    The fix: Give the input a real label — a hidden one is fine, as long as it is read aloud.

    For your developer
    Criterion
    WCAG 3.3.2 Labels or Instructions
    Rule
    label · 1 element on every page
    Element
    <input type="search" name="q" placeholder="Search">
    What it found
    No associated <label>, no aria-label. A placeholder is not a label: it vanishes as soon as the user types.
  3. Critical

    The cart button is an icon with nothing behind it

    The basket in the header is just a picture. Screen readers announce “link” and nothing else, so a blind shopper can fill a basket and never find the way to pay. This is the one that costs you the sale.

    The fix: Give the link a name — “Cart, 2 items” — either as visible text or a hidden label on the icon.

    For your developer
    Criterion
    WCAG 4.1.2 Name, Role, Value
    Rule
    link-name · 1 element on every page
    Element
    <a href="/cart"><svg class="icon-bag">…</svg></a>
    What it found
    Link has no accessible name: the SVG is not labelled and there is no text alternative.

The report also lists what it could not decide — things like whether an animation respects a reduced-motion setting — as “needs review” rather than counting them as failures. And it says plainly that it is not a certification and not legal advice.

Run this on your storeFree, and it takes under a minute.

Monitoring

€29 a month, once the first month is up

You fix the list once. Then you add a theme update, a new app, a campaign banner, and something quietly breaks again. Monitoring keeps the check running.

  • The same key pages, scanned again each month, so a theme update that breaks your menu gets caught.
  • A change log that separates what’s new from what’s fixed — progress you can see, not just a score.
  • Every new failure written the same way: the page, the element, who it blocks and the fix.
  • Cancel any time. No contract, no setup fee.

Monitoring covers the same key pages on a monthly cycle. It is not a certification and it does not cover pages behind a login, the checkout beyond the first step, or your mobile apps.

Who it’s for

Built for shops of 10 to 500 products

Stores on Shopify or WooCommerce

Shopify and WooCommerce stores, and the small agencies that build them. Big enough that accessibility is a legal question, small enough that a €5,000 agency audit and a Siteimprove licence are not realistic.

Agencies and freelancers who build those stores

You ship Shopify and WooCommerce themes. Scan the build before you hand it over, fix what the report finds, and give the client a document that shows what was checked. Re-scan on retainer with monitoring.

What Kerb is not: not an overlay widget, not a certification, and not a substitute for a human audit if you are already in a legal dispute. It is an automated scan of your key pages, explained so that someone can act on it.

For agencies

Scan the build before your client does

If you build Shopify or WooCommerce stores, accessibility is a question you will be asked — by the client, or by their lawyer. It is a much cheaper conversation before launch than after.

  • Check it while it’s still yours

    Run the scan on a staging build and fix the problems before launch, not after.

  • Hand over the PDF

    Hand over the PDF as part of your delivery. Your name on the work, our scan behind it.

  • Keep it fixed on retainer

    Keep it fixed on retainer: monthly re-scans and a change log you can show them.

Priced per store, not per seat: €49 covers one store’s report and its first month of monitoring. Scan the stores you build and skip the ones you don’t. Today that means one report and one payment per store — there is no agency dashboard for managing several in one place.

Why now

The rules already apply

European Accessibility Act

In force since June 2025 and it covers online shops selling into the EU. The exemption for micro-businesses is narrow, and “we’re only small” is not a defence once a customer complains.

United States

ADA demand letters reach retailers of this size, and the first one usually arrives with a deadline attached.

We are a scanning tool, not lawyers, and none of this is legal advice. If you have received a letter, speak to a lawyer — and bring the report with you.