nextlevels logo
DEEN

Check accessibility: The free BFSG check

A real browser tests your home page and one subpage against WCAG 2.2 AA – plus the disclosures the BFSG requires.

  • Page views only, no login
  • No signup
  • 60 seconds at most
  • Not legal advice

Featured on Ziel: barrierefrei (German)

Public websites only. The check tests two pages, also loads the accessibility information and takes 60 seconds at most.

  • WCAG 2.2
  • EN 301 549
  • BFSG § 14
  • axe-core
  • Chromium
  • As of 3 Oct 2026

Featured on

  • Featured on Twelve Tools
  • Featured on LaunchIgniter
  • Listed on Turbo0
  • BFSG Accessibility Check badge

What the check tests

Five checks in one run. Each measures something that can be established automatically with certainty – the rest we show you honestly as a manual task.

  • Contrast

    Can text be told apart from its background well enough?

  • Alternative text

    Do images have a description for screen readers?

  • Labels

    Form fields, buttons and links with names, headings, language, ARIA.

  • Accessibility information

    Linked, reachable, with the items from Annex 3?

  • Cookie banner & contact

    Reachable by keyboard? Can users report barriers?

Your result in seconds

Score and all findings right away. With your email you also get element, selector, rule and fix for every finding.

Check now
Sample resultexample-shop.com · 2 pages
Automated score

64/100

Critical

1

BFSG disclosures

1/3

  • Images without alternative textEN 301 549 9.1.1.1
  • Button contrast 1.6 : 1EN 301 549 9.1.4.3
  • No accessibility informationSection 14 BFSG
  • Cookie banner not reachable by keyboardBFSG disclosure
Example with a made-up domain, not a real test result.

How the check runs

A Chromium browser opens your pages like a visitor, tests them with axe-core and looks for the three BFSG disclosures.

  • Home page
  • Subpage
  • Cookie banner
  • – one after the other, one browser

What an automated test can do – and what it cannot

An automated test finds only part of the barriers. It does not confirm BFSG compliance and is not legal advice.

What the check tests

automated

Since 28 June 2025, Germany's accessibility act (BFSG) has required many online shops and digital services to be accessible. The check opens your home page and one subpage in a real browser and tests them against WCAG 2.1 and 2.2, levels A and AA.

  • Color contrast of text
  • Whether images have alternative text
  • Labels of form fields, buttons and links
  • Headings, page structure and page language
  • ARIA roles and attributes
  • Further axe-core rules for WCAG 2.1 and 2.2, levels A and AA
  • Accessibility information: whether the home page links to it, whether it can be reached and whether keywords for the items in Annex 3 BFSG appear
  • Contact: whether there is a contact link, an email address or a contact form through which users can report barriers
  • Cookie banner: axe-core rules inside the banner, whether the Tab key reaches it and whether its buttons have names

What needs a manual review

manual

Automated tests find only part of the barriers. The check reliably shows the errors that can be measured. Whether people with disabilities can really use your website only shows in a manual review.

  • Keyboard operation: every function without a mouse, visible focus, sensible order
  • Screen reader: whether alternative texts, labels and status messages make sense
  • Video and audio: captions, audio description, transcripts
  • Flows such as checkout, login and forms with error messages
  • Content behind a cookie banner or login, in iframes and in PDFs
  • Every page other than the two checked
  • Whether the accessibility information is correct and complete

The check therefore does not promise that your website complies with the BFSG. Not legal advice.

BFSG: who is affected and what the law requires

The key points in brief, each with its reference in the German act. Whether your offer falls under the law is a question for your legal counsel.

As of 3 October 2026. Not legal advice.

Who is affected

Section 1 (3) no. 5 · section 2 no. 26
The BFSG applies to e-commerce services provided to consumers after 28 June 2025 (section 1 (3) no. 5 BFSG). That means websites and apps through which consumers conclude contracts (section 2 no. 26 BFSG), for example online shops.

The exemption

Section 3 (3) · section 2 no. 17
Microenterprises that offer services are exempt (section 3 (3) BFSG). A microenterprise employs fewer than ten people and has an annual turnover or annual balance sheet total of no more than EUR 2 million (section 2 no. 17 BFSG).

The accessibility information

Section 14 · Annex 3
Providers must state in their terms and conditions, or in another clearly noticeable place, how their service meets the requirements (section 14 BFSG, Annex 3). This includes a description of the service, explanations of how it is carried out, a description of how the requirements are met and the competent market surveillance authority. This information must itself be accessible.

The technical benchmark

Section 4 · EN 301 549
In practice EN 301 549 and WCAG serve as the benchmark; the act itself refers to harmonized standards (section 4 BFSG). For websites, EN 301 549 adopts WCAG 2.1, levels A and AA.

The score

0 to 100

The check uses axe-core, Deque's open-source testing library. Every rule belongs to a WCAG success criterion and has a severity.

The score is the weighted share of passed rules from 0 to 100. Critical rules count 10, serious 7, moderate 3 and minor 1. A rule counts as failed as soon as it reports a violation on one of the pages checked. Rules that find nothing to test on the pages are left out. With at least one critical finding the score is capped at 79.

The score compares automated rules only. 100 means: no automatically measurable violation on the pages checked. The BFSG disclosures do not count toward the score.

The severity

from axe-core
  • Critical: blocks some users completely
  • Serious: makes use considerably harder
  • Moderate: gets in the way, but can usually be worked around
  • Minor: small flaw

The classification comes from axe-core.

The report

instant + email
  • Right away: score, all findings with severity and number of affected elements
  • Right away: BFSG disclosures as three status rows (accessibility information, contact, cookie banner), separate from the score
  • After email: affected elements with selector and HTML snippet
  • After email: explanation of the rule, WCAG success criterion with its EN 301 549 clause and fix hint
  • Rules axe-core could not decide with certainty, as a list for manual review

FAQ about the BFSG check

Your question isn't here?

Ask directly

Is my website BFSG-compliant if the check shows 100?

No. 100 only means that axe-core found no automatically measurable violation on the two pages checked. Keyboard operation, screen reader clarity, captions and flows such as the checkout can only be tested manually. The check therefore does not confirm BFSG compliance and is not legal advice.

Who does the BFSG apply to?

Germany's Accessibility Strengthening Act has applied since 28 June 2025, among other things to e-commerce services, meaning websites and apps through which consumers conclude contracts, for example online shops. Microenterprises that offer services are exempt: fewer than ten employees and an annual turnover or annual balance sheet total of no more than EUR 2 million. Whether your offer is covered is a question for your legal counsel. As of 3 October 2026.

What exactly does the BFSG check test?

It opens your home page and one more page from your sitemap.xml in a Chromium browser and tests both with axe-core against the rules for WCAG 2.1 and 2.2, levels A and AA. This covers color contrast, alternative text, labels of form fields, buttons and links, the heading structure and ARIA attributes. On top come three BFSG-specific checks: whether accessibility information is linked and reachable, whether there is a way to get in touch and whether the cookie banner can be reached by keyboard. They appear in the report separately from the score.

How can I test my website for accessibility?

In two stages. An automated test like this check finds measurable errors in seconds. The manual review follows: operate the website with the keyboard only, go through it with a screen reader and test flows such as ordering or the contact form from start to finish.

What is the accessibility information?

Under section 14 BFSG and Annex 3, providers must state in their terms and conditions, or in another clearly noticeable place, how their service meets the accessibility requirements. This includes a description of the service, explanations of how it is carried out and the competent market surveillance authority. The check does not write this information.

Does the check test my accessibility information?

It looks for a link to the accessibility information on the home page, loads the page and checks whether it can be reached and has no critical or serious axe-core findings of its own. It also looks for keywords for the items in Annex 3 BFSG: a description of the service, how the requirements are met and the competent market surveillance authority, plus a date. These are hints for a manual review. The check does not judge whether the information is correct and complete.

Why does the check test the cookie banner?

The banner appears in front of the content. If the keyboard cannot reach it or its buttons have no name, many users never get to the page at all. The check therefore tests the banner with axe-core, presses the Tab key up to 30 times and looks whether the focus lands in the banner. It clicks nothing and accepts no cookies.

What does the EN 301 549 clause in the report mean?

EN 301 549 is the European standard for accessible information and communication technology. For websites, its chapter 9 takes over the success criteria of WCAG 2.1, levels A and AA, under the same number: WCAG 1.4.3 corresponds to clause 9.1.4.3 (EN 301 549 V3.2.1). The report shows the clause next to the WCAG criterion. Criteria that only exist since WCAG 2.2 have no clause in this version.

What data do you store?

Without an email we store no result; the scanner only logs the domain, the duration and whether the request succeeded. If you request the report, we store your email address, the URL and the score to send you the report and to get in touch once.

What happens next?

The report is the start. This is how it continues:

Contrast, missing alternative text and labels are often something your team can correct itself. The report names the element, the rule and a fix hint.

Profile picture of Slawa Ditzel, Executive Partner

Slawa Ditzel

Executive Partner

  1. You send the report or the domain
  2. We tell you which findings count first
  3. Audit, implementation or your team – you decide

+49 (0) 2161 539 71 60info@next-levels.de