Accessibility scanning

All access for every store

Allcess crawls your whole storefront with axe-core, then turns what it finds into a work list grouped by fix. It reads your store from the outside, so there is nothing to install.

The European Accessibility Act may apply to your store, depending on your size and where you sell. Very small businesses can be exempt. We are not a law firm, so check with someone who is.

An animated introduction to Allcess. A store address is typed in and a scan starts. The crawler works through 40 pages while the findings count climbs to 478. Those 478 findings then gather into 5 groups, one per fix. The report lists the 5 issues by severity and opens the first one, buttons with no label, to show the fix: one edit in the header template that clears it on all 40 pages. It ends with the dated PDF report and weekly re-scans whose results fall from 478 to 31.

The old way

Most accessibility tools give you a wall of findings

A scanner reports every failing element it sees. On a storefront that means hundreds of entries, most of them the same template repeating. It looks like an enormous problem and tells you nothing about where to start.

Without Allcess

478

findings, listed page by page

Forty pages to open one at a time, with no way to tell that the same header is responsible for most of it.

With Allcess

5

issues to fix, ranked by leverage

The same scan, grouped by rule. Two of the five sit in your header template, so one edit clears them across every page.

Real figures from a scan of a live Shopify storefront.

The report

What you get back

Every issue, ordered by severity, with the pages each one touches and what to change. Here it is as the PDF you can hand to whoever maintains your store.

A scroll through an exported Allcess PDF report, at double speed. It opens with a summary of 9 issues by severity and a table of the 20 pages scanned, then gives each page's findings in turn, each with its rule, severity and example elements.

How it works

From a URL to a work list

  1. Step 1

    Add your URL

    We check the site is reachable before saving it. There is nothing to install on your store.

  2. Step 2

    We crawl it

    A real browser loads up to 100 pages of your site and runs axe-core against each one, the same engine inside Chrome DevTools.

  3. Step 3

    You get a work list

    Findings grouped by what actually needs fixing, sorted by severity, written without the jargon.

What we check

30 checks, run on every page

All of them real axe-core rules. We list what we can't catch just as plainly.

  • Images without a text description

    image-alt

  • Image buttons without a label

    input-image-alt

  • Image map areas without a label

    area-alt

  • Links with no readable text

    link-name

  • Buttons with no accessible label

    button-name

  • Submit buttons with no value

    input-button-name

  • Links only distinguished by colour

    link-in-text-block

  • Form fields with no associated label

    label

  • Fields with conflicting labels

    form-field-multiple-labels

  • Dropdowns with no accessible name

    select-name

  • Invalid autocomplete attributes

    autocomplete-valid

  • Text with too little contrast

    color-contrast

marks checks that come with written fix guidance, tailored to Shopify or WooCommerce when we detect one.

See every check, and what we can't catch

The product

Six things that make it useful

The parts that decide whether a scan turns into fixed pages.

It crawls, it doesn't sample

Most free checkers look at one URL. Allcess follows your internal links and scans up to 100 pages, so problems on product and checkout pages surface too.

Up to 100 pages per scan

Findings grouped by fix, not by page

One bad template repeats on every page. We roll findings up by rule and show how many pages each one touches, so you can see which single change clears the most.

478 findings → 5 real fixes

Fix guidance, not just rule names

Each finding comes with what to change and why it matters. When we detect Shopify or WooCommerce, the guidance names the theme files you'd actually edit.

17 rules with written guidance

A dated record you can hand over

Every scan exports to a PDF with the date, the pages covered and what was found. Useful when someone asks what you've been doing about accessibility.

PDF export on every scan

Re-scans on a schedule

Sites drift. Set a site to re-scan daily, weekly, monthly or yearly and the history builds itself, so a regression shows up as a rising line.

Daily to yearly

We scan ourselves too

Allcess runs its own scanner against this site. It found real problems in our buttons and list markup, and we fixed them before shipping this page.

Scanned in both themes

Security

We read your pages, we don't touch them

Allcess loads public pages the way a visitor's browser would and only ever reads them. Your scan history is yours, and deleting your account deletes it.

How we handle your data
  • Read-only. We never modify your site
  • Passwords hashed with bcrypt, screened against breach corpora
  • Changing your password signs out every other device
  • Your data is never used to train anything

FAQ

The questions worth asking

  • No, and be wary of any tool that says otherwise. Automated testing catches somewhere between a third and a little over half of real accessibility problems. The rest needs a person using the site. Allcess gives you a dated record of what an automated scan found, which is evidence of effort, not a certificate of compliance.

Get started

See what's actually on your site

Add your store's address and have a full scan back in minutes.

  • Crawls your whole storefront, not just the homepage
  • Findings grouped by fix, not by page
  • Fix guidance tailored to Shopify and WooCommerce
  • A dated PDF record of every scan