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.
Related services for accessibility
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 now64/100
1
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
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 exemption
Section 3 (3) · section 2 no. 17
The accessibility information
Section 14 · Annex 3
The technical benchmark
Section 4 · EN 301 549
How the BFSG check scores
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
More tools & checks
Is my website BFSG-compliant if the check shows 100?
Who does the BFSG apply to?
What exactly does the BFSG check test?
How can I test my website for accessibility?
What is the accessibility information?
Does the check test my accessibility information?
Why does the check test the cookie banner?
What does the EN 301 549 clause in the report mean?
What data do you store?
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.
We test with keyboard and screen reader what the automated run cannot see: navigation, forms, checkout, media. You get a prioritized list by WCAG success criteria.
We remove the barriers in theme, components and content and supply the technical details for your accessibility information. The legal review stays with your legal counsel.

Slawa Ditzel
Executive Partner
- You send the report or the domain
- We tell you which findings count first
- Audit, implementation or your team – you decide