Zum Inhalt springen
BFSG compliance since 2025

Blog

Accessible Authentication per WCAG 2.2 (SC 3.3.8)Cognitive function tests at sign-in are not permitted unless an alternative existsCognitive test = barrierTranscribe a distorted CAPTCHADecipher and re-type the charactersRecall a password from memoryMemory task without a password managerRe-type a one-time code by handCopy characters from an SMS or appConformant paths (SC 3.3.8)Alternative: passkey or magic linkLog in without recall or typing taskMechanism: password managersUse autocomplete, allow pastingObject recognition: everyday itemsCar, traffic light, dog instead of textPersonal content: user's own imageContent the user provided themselvesTwo levels, one goal: sign-in without a cognitive hurdleSC 3.3.8 - Level AAException allowed with alternativeSC 3.3.9 - Level AAAobject recognition also disallowed2xhow much more often disabledusers flag CAPTCHA as a barrier(WebAIM Survey 10, 2024)SC 3.3.8 is Level AA - the benchmark EN 301 549 adopts with version 4.1.1 (2026)94.8% of home pages show WCAG errors - accessible logins prevent abandonment (WebAIM Million, 2025)
WCAG 2.2 Jul 15, 2026

Accessible Authentication: CAPTCHA Alternatives (SC 3.3.8)

Accessible sign-in under WCAG 2.2 SC 3.3.8: password managers, magic links, passkeys and low-barrier CAPTCHA alternatives using object recognition and audio.

13 min read Read →
Accessible Cookie Banner: where consent failsCookie SettingsWe use cookies for statistics and comfort.Your choice applies to this website.First contact with the site, often before any contentAccept allRejectvisually weighted weakerNo focus trapFocus moves behindthe open dialogKeyboard blockedButtons not reachableby Tab (2.1.1)Contrast too lowReject button below4.5:1 (1.4.3)No announcementNo role=dialog,no accessible name79.1%of home pages showlow text contrast (WebAIM)4.5:1minimum contrast for texton buttons and labels (WCAG 2.2)3:1minimum contrast forcontrols (WCAG 1.4.11)How the consent dialog passes the testKeyboard operable, visible focus, reject equal to accept
BFSG-Compliance Jul 13, 2026

Accessible Cookie Banners: WCAG 2.2 and BFSG Compliance

Cookie banners are the first interaction and fall under the BFSG. Where consent banners fail WCAG 2.2 and how to make them accessible and compliant.

12 min read Read →
Micro-Enterprise Exemption: Who Is Really Exempt?Your businessFewer than 10 employees?(BFSG Section 3)At most EUR 2 millionturnover or balance sheetMicro-enterpriseboth criteria metServices only: exemptNo BFSG duty for the serviceProvide facts on requestVoid as soon as products are addedProducts in range: obligatedOnline shop with BFSG productsThe exemption does not applyAccessible per EN 301 549 / WCAG 2.2Not a micro-enterprise? The only fallback is BFSG Section 17Prove disproportionate burden, document it, keep it 5 years, reassess every 5 years
BFSG-Recht Jul 10, 2026

BFSG Micro-Enterprise Exemption: Who Is Exempt?

Many businesses assume that as a micro-enterprise they are BFSG-exempt. When the exemption applies, why it covers services only and what Section 17 demands.

13 min read Read →
One Interface, Two Platforms Made AccessibleiOS · VoiceOverBuy now„Buy now,button“Tap target 44 ptAText up to 200 %Android · TalkBackBuy now„Buy now,button“Tap target 48 dpAText up to 200 %Shared StandardEN 301 549 · Chapter 11WCAG 2.1 · Level AAbinding since 2025applies to both platformsFour Duties for Every AppScreen reader labelsVoiceOver, TalkBackTap targets44 pt / 48 dpContrast and text4.5:1 · up to 200 %No gesture-only useSingle-pointer path
App-Barrierefreiheit Jul 8, 2026

Accessible Apps: BFSG Rules for iOS and Android

The BFSG now covers native apps too. What iOS and Android apps must meet for WCAG 2.1 AA and EN 301 549: labels, tap targets, contrast and focus order.

14 min read Read →
Accessibility Overlays: Surface, Not SubstanceAn overlay widget changes the display, not the source codeWhat an Overlay ChangesFont size and line spacingColor scheme and contrast filtersRead-aloud and focus helpers in the browserOnly the display, at runtime in the browserWhat an Overlay Does Not FixMissing text alternatives in the markupInoperable forms and focus trapsWrong semantics and ARIA structureCauses lie in the source code, not the display67%of experts rate overlays ashardly or not effective (WebAIM)~40%of WCAG issues are evenautomatically detectable (WebAIM)1031experts call for moving awayfrom overlays (Overlay Fact Sheet)WCAG 2.2 AA is built in the source code and editing, not at the push of a button
BFSG-Compliance Jul 6, 2026

Accessibility Overlays: Why They Fail BFSG Compliance

Accessibility overlays promise one-click BFSG compliance but only change the surface. Why studies, the DBSV and authorities reject them and what truly works.

12 min read Read →
Accessibility as an Editorial Process: Gates, Not Rework1Image uploadAlt text mandatoryor mark decorativeWCAG 1.1.1 met1.1.12StructureHeadings H1 to H3no skipped levelsWCAG 1.3.1 / 2.4.61.3.13Link textdescriptive targetsno "click here"WCAG 2.4.4 met2.4.44PDF and languagetagged PDF, plainlanguage where neededEN 301 549 metPDF/UAPublishaccessible from day oneSpot check and monitoring: no re-barrieringTraining matrix: who learns what on the editorial teamRoleFocus of the trainingCadenceEditorsAlt text, link text, heading structureOnboardingSubject authorsPlain and easy-to-read language, tablesTwice a yearDesign and layoutContrast, image types, tagged PDFsTwice a yearAccountable leadsBFSG duties, statement, feedbackYearlyMissing alt text on 55.5 percent and skipped headings on 39 percent of home pages (WebAIM Million, 2025)
Schulung Jul 3, 2026

Accessible Content: Training for Your Editorial Team

Accessibility is an ongoing editorial process: train alt text, link text, headings and accessible PDFs in the team to prevent the gradual re-barriering of your site.

13 min read Read →
Accessible AI chatbot: from dialog to screen reader outputAISupport assistantrole=log, aria-live=politeBot, 2:02 pmHow can I help you?You, 2:02 pmWhere is my order?Bot, 2:03 pmYour shipment is on its way.Delivery tomorrow by 6 pm.Type a message ...Play audioRead as textSend (Enter)Focus stays in the input fieldno jump to the top of the pageWhat the screen reader announcesLog: bot says, shipment is on its wayNew message, 2:03 pm, from assistantInput field, type a message, editablepolite: waits for a pause, does not interruptFour pillars of conformance1KeyboardTab, Enter, Escapefully operable without a mouse2Live regionrole=log, politenew replies are read out3Focusno focus lossstays in the dialog after sending4Text pathalternative to audiovoice bot also delivered as text
WCAG Jul 1, 2026

Accessible AI Chatbots: WCAG-Compliant Voice Bots

Why AI chatbots and voice assistants fall under the BFSG and how conversational UI becomes WCAG-compliant with ARIA live regions and focus management.

14 min read Read →
Weighing Audit Cost Against BFSG RiskPlannable Investment: WCAG 2.2 AuditSmall website (5-20 pages)1,500-4,000 EURCorporate site (20-50)4,000-8,000 EUROnline shop (50-200)8,000-15,000 EURWeb application (200+)from 15,000 EURMonitoring per year1,000-3,000 EURUnplannable Risk Without ProofFine ceiling (Section 37)up to 100,000Standard violationsup to 10,000Compliance of German sites0 %Abandonment due to barriers80.7 %Conversion when accessible+15 %From Audit to a Robust Proof1Sampling2Full audit3Remediation4Monitoring5Proof
BFSG Jun 29, 2026

Accessibility Audit Cost 2026: Prices, ROI, Funding

What a WCAG 2.2 audit costs in 2026: prices by scope, sampling versus full audit, monitoring, the BFSG fine ceiling, conversion ROI and funding at a glance.

13 min read Read →
Accessible Route Changes in a Single-Page App1. Link activatedClick / Enter on linkRoute changes, no reload2. Router renders viewSet document.titleNew content in the DOM3. Set focusfocus() on H1 / regiontabindex=-1 on target4. Announcementaria-live=politeScreen reader reads titleapp.com/home -> app.com/productsWithout focus managementFocus stays stuck on the old link.Screen reader does not announce the change.With focus managementH1: Products (focus, visible ring)Focus on the new heading,title is read out.Three central WCAG references2.4.3 Focus OrderFocus follows the route change sensibly.4.1.3 Status MessagesLive region announces the new view.2.4.2 Page Titleddocument.title reflects the route.Frameworks: React, Vue, Angular, Svelteall need a deliberate focus concept.95.9 percent of home pages had WCAG failures in 2024, averaging 56.8 per page (WebAIM Million, 2024)
WCAG Jun 26, 2026

Focus Management in Single-Page Apps, Accessibly

Accessible route changes in single-page apps: move focus to the new heading, keep the page title in sync and announce view changes via a live region per WCAG 2.4.3.

14 min read Read →