Skip to content

Does your website pass the BFSG?

The Barrierefreiheitsstärkungsgesetz has applied since June 28, 2025, and most SMB websites fail it. Enter a URL and get a WCAG 2.1 AA scan from a real browser, sorted by what to fix first.

Renders the page in a real browser; allow 10 to 30 seconds. Not a conformity assessment, nothing stored.

What this checks

Real browser

The page is rendered in headless Chromium and tested with axe-core, the industry-standard engine.

WCAG 2.1 AA

The rule set behind EN 301 549, the technical baseline the BFSG points to.

Worst first

Violations sorted by impact, grouped by WCAG principle, each with the affected elements and a fix link.

Honest scope

Automated testing finds only part of all issues. A clean result is necessary, not sufficient.

BFSG gaps to close?

We remediate accessibility in the codebase: semantics, contrast, keyboard paths, and checks in CI so the fixes stay fixed.

Questions about the Barrierefreiheits-Check (BFSG)

What does the BFSG require from websites?

The Barrierefreiheitsstärkungsgesetz has applied since 28 June 2025 to many consumer-facing digital services, online shops included. Websites have to meet the accessibility requirements of EN 301 549, which builds on WCAG 2.1 level AA. Micro-enterprises that provide services are exempt.

What does the check test?

It loads the page in a real browser and runs axe-core with the WCAG 2.1 A and AA rules: color contrast, alt text, form labels, heading and landmark structure, accessible names for links and buttons, the page language, and more. Violations are sorted by impact and grouped by WCAG principle.

Can an automated test prove BFSG compliance?

No. Automated rules catch part of WCAG, mostly structural issues. Keyboard flow, screen reader output, and plain language need a manual review. The result is a starting point, not a conformity assessment.

How is the score calculated?

Each violated rule costs points by impact, from a base of 100: 16 for critical, 10 for serious, 4 for moderate, and 1 for minor.

From the blog

Contact

What eats your team's time?

Two or three sentences are enough. Philipp reads every message himself and usually replies within two business days.

Philipp Kant

Philipp Kant
Software & AI Architect, Krefeld

What is it about?

Opens your email app with the message to philipp@kant.dev, ready to send. You see everything before it goes out. Privacy policy

  • No sales call unless you ask for one.
  • No newsletter, no automated follow-ups.
  • Your message goes to one inbox: philipp@kant.dev.

Rather talk? Pick a 30-minute slot

Or write directly: philipp@kant.dev