Free tool

Accessibility report summary

Paste the axe JSON your team already produces and see which findings the European Accessibility Act actually requires you to fix, which sit on checkout or login, and which are advice.

Your axe JSON report

{
  "url": "http://localhost:3100/practice/shop/checkout",
  "violations": [
    {
      "id": "label",
      "impact": "critical",
      "tags": [
        "cat.forms",
        "wcag2a",
        "wcag412",
        "section508",
        "section508.22.n",
        "TTv5",
        "TT5.c",
        "EN-301-549",
        "EN-9.4.1.2",
        "ACT",
        "RGAAv4",
        "RGAA-11.1.1"
      ],
      "description": "Ensure every form element has a label",
      "help": "Form elements must have labels",
      "helpUrl": "https://dequeuniversity.com/rules/axe/4.13/label?application=playwright",
      "nodes": [
        {
          "html": "<input id=\"postal\" data-testid=\"postalCode\" autocomplete=\"postal-code\" class=\"w-full border border-rule-strong bg-paper px-3 py-2.5 font-sans text-base text-ink focus:border-ink focus:outline-none\" value=\"\">",
          "target": [
            "#postal"
          ],
          "failureSummary": "Fix any of the following:\n  Element does not have an implicit (wrapped) <label>\n  Element does not have an explicit <label>\n  aria-label attribute does not exist or is empty\n  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n  Element has no title attribute\n  Element has no placeholder attribute\n  Element's default semantics were not overridden with role=\"none\" or role=\"presentation\"",
          "impact": "critical"
        }
      ]
    }
  ],
  "testEngine": {
    "name": "axe-core",
    "version": "4.13.0"
  }
}

Everything happens in your browser. The report is not uploaded, which matters here: an axe report contains the HTML of the elements that failed.

How to get a report

Ask your team for the JSON their accessibility scan already produces, or run one: npx @axe-core/cli https://your-site/checkout --save report.json. With Playwright, new AxeBuilder({ page }).analyze() returns the same object — see accessibility testing with axe and a keyboard. Reports from several pages can be pasted as one JSON array.

Issue types the standard requires you to fix

1 element across 1 page

On checkout, login, or payment: 1
WCAG criteria failing: 1
Advisory, not the baseline: 0

Scanned with axe-core 4.13.0

Required — fix these first

Form elements must have labels
critical · 1 element
A screen reader cannot tell the person what to type here, so the form cannot be completed.
Forms and controlsWCAG 4.1.2Identification, security, or paymentHow to fix it
http://localhost:3100/practice/shop/checkout

What a scan cannot tell you

Whether a label makes sense, only whether one exists.
Whether the tab order follows the order things appear on screen.
Whether an error message explains what to do.
Whether the flow can actually be completed with a keyboard, or with a screen reader.

Those need a person. The five-minute version is in what the European Accessibility Act requires of your checkout.

How it decides what is required

The European Accessibility Act points at EN 301 549, which incorporates WCAG 2.1 Level AA. axe-core tags each of its rules with the standards it belongs to, so this tool does not maintain its own opinion about scope: a finding is required when axe tags the rule EN-301-549, and advisory when it does not.

In axe-core 4.13.0 that tag is on 69 of its 105 rules, and it covers exactly the same rules as the WCAG 2.1 A and AA tags — not one more, not one fewer. A unit test reads axe-core and fails if those two sets ever drift apart, because at that point the tool would be telling people the wrong thing about a legal obligation.

The rules left out are tagged best-practice, wcag2aaa, wcag22aa, or experimental. They are worth fixing. They are not the baseline, and putting them in the same list is how a required finding ends up behind eleven suggestions.

Why checkout and login are called out

The Act names identification, security, and payment explicitly for e-commerce, so a violation on those pages carries more weight than the same violation on a marketing page. This tool spots them from the URL — paths containing checkout, cart, payment, login, account and similar. A checkout served from /c/1 will be missed, which makes that count a floor rather than a total.

What this is not

It is not a compliance audit, and it is not legal advice. An automated scan checks what can be checked mechanically, and a clean scan is the floor rather than proof of anything — our walkthrough with axe and a keyboard includes a bug that passed every automated check and still broke the page. For why the deadline matters and what enforcement has looked like so far, read what the European Accessibility Act requires of your checkout.