app-entwickeln-lassen.de LogoApp entwickeln lassen

Legal, Privacy & Security

BFSG and Apps: What Germany's Accessibility Act Requires

app-entwickeln-lassen.de editorial team 6 min read
Contents
  1. What is the BFSG?
  2. Which apps fall under the BFSG?
  3. What exactly is required?
  4. BFSG check for your app in six steps
  5. Effort and cost of implementation
  6. What happens in case of violations?
  7. Conclusion
  8. Frequently Asked Questions

Germany's Accessibility Strengthening Act (Barrierefreiheitsstärkungsgesetz, BFSG) has applied since 28 June 2025 and requires many providers to make their apps accessible, particularly in e-commerce, consumer banking and passenger transport. Apps through which consumers conclude contracts are the main focus. This article explains whether your app falls under the BFSG, which requirements apply and how to approach it pragmatically.

What is the BFSG?

The BFSG transposes the European Accessibility Act (Directive (EU) 2019/882) into German law. Its aim is that people with disabilities can use certain products and services without outside help. Unlike earlier rules that mainly targeted public bodies, the BFSG addresses private companies. It is fleshed out by an ordinance (BFSGV) that describes the requirements for products and services in detail. Other EU member states have adopted their own laws implementing the same directive, so the principles are similar across the EU.

This article is a practical overview and not legal advice. If in doubt about whether and to what extent your app is affected, have it reviewed by a lawyer.

Which apps fall under the BFSG?

For app providers, the services covered by the law are most relevant. The app is often the access channel to the service.

AreaTypical appsAffected?
E-commerce servicesShopping apps, booking apps, apps with paid subscriptions or orders for consumersusually yes
Consumer banking servicesBanking apps, payment and credit appsyes
Passenger transportTicket apps, timetable and travel information apps from transport operatorspartly, depending on the mode of transport
Electronic communicationsMessaging and telephony services from electronic communications providersyes
E-books and audiovisual mediaE-book apps, access to streaming servicesyes
Pure B2B apps, internal employee appsField service, warehouse or HR appsusually no
Information apps without contract conclusionCompany info, magazines without purchasemostly no, check case by case

Micro-enterprise exemption: service providers with fewer than ten employees and an annual turnover or balance sheet total of no more than two million euros are exempt from the service requirements. Note that this exemption does not apply in the same way to products, and voluntary accessibility still makes sense for small providers.

There are also transitional rules, for example for services provided using products already in use before the deadline. Rely on these only after careful review; for apps under continuous development, implementing the requirements is the safer route anyway.

What exactly is required?

The BFSG requires services to be perceivable, operable, understandable and robust. Technically, practice follows the harmonised standard EN 301 549, which for web and app content largely references WCAG 2.1 at level AA. For apps this means, among other things:

  • Screen reader support: all controls have meaningful labels for VoiceOver (iOS) and TalkBack (Android).
  • Scalable text: the app works with enlarged system font sizes without cutting off content.
  • Sufficient contrast: at least 4.5:1 for normal text under WCAG AA.
  • Not colour alone: errors and status are also conveyed through text or icons.
  • Large enough touch targets and no functions operable only through complex gestures.
  • Understandable forms: visible labels, clear error messages, help with corrections.
  • Media alternatives: captions for videos, text alternatives for informative images.
  • Accessible payment and login flows: no CAPTCHA barriers without an alternative, support for password managers.

Service providers must also publish information on how their service meets the accessibility requirements, often as an accessibility statement in the terms and conditions or another easily accessible place.

BFSG check for your app in six steps

  1. Clarify applicability: does the app offer one of the covered consumer services? Does the micro-enterprise exemption apply?
  2. Define critical user journeys: registration, login, search, cart, payment, account management, contact.
  3. Automated testing: accessibility scanners and linters for iOS and Android quickly find missing labels and contrast issues.
  4. Manual testing: walk through every critical journey completely with VoiceOver and TalkBack and with maximum font size.
  5. Prioritise and fix issues: blockers in payment or login first.
  6. Document and embed: publish accessibility information, add checks to the definition of done and to automated tests.

Our article on building accessible apps covers the technical implementation. How coding agents can help with testing is described in agentic coding and accessibility.

Effort and cost of implementation

For new apps, accessibility is mainly a matter of the design system and development discipline; the extra effort stays moderate if it is planned from the start. For existing apps the effort depends heavily on their condition: apps built with standard controls can often be improved significantly within a few days, while heavily customised interfaces, canvas-based rendering or older WebView solutions may require larger rework. If a redesign is coming anyway, build accessibility into it directly. You can get a fixed-price offer for review and implementation after a free analysis through our offer wizard.

What happens in case of violations?

Compliance is monitored by the market surveillance authorities of the German federal states. They can demand corrections, ultimately order a service to be discontinued and impose fines. Consumers and associations can also report violations and initiate proceedings. Regardless of the legal risk, accessible apps are easier for everyone to use, for example in bright sunlight, one-handed or for older people.

Agentic coding workshop for your team? From €799 net – request a quote by e-mail

Conclusion

The BFSG makes accessibility mandatory for many consumer apps, especially in e-commerce, banking and passenger transport. First check whether your app is affected, then focus on the critical user journeys. With WCAG 2.1 AA as the benchmark, manual screen reader testing and a firm place in your development process, accessibility turns from a project risk into a quality feature.

Frequently Asked Questions

Since when does the BFSG apply to apps?

The BFSG has applied since 28 June 2025. Since then, covered products and services newly offered must meet the accessibility requirements; transitional periods exist for certain situations.

Does my B2B app have to be accessible?

The BFSG targets products and services for consumers, so pure B2B apps are usually not covered. Check whether the app is also open to private customers; this article is not legal advice.

Which standard applies to accessible apps?

In practice, EN 301 549 serves as the benchmark, and for apps it largely references WCAG 2.1 level AA. Meeting these criteria gives you a solid basis for compliance.

Does the BFSG apply to small companies?

Micro-enterprises with fewer than ten employees and an annual turnover or balance sheet total of no more than two million euros are exempt for services. All other providers of covered services must meet the requirements.

This article was written by the editorial team of app-entwickeln-lassen.de – the app and AI development service of jocapps GmbH, based in Freiburg, Germany, and building apps since 2014. The content is for general information and does not replace individual (legal) advice.

You might also like

Legal, Privacy & SecurityEU AI Act for Apps: What Providers of AI Features Must Know

EU AI Act and apps: risk categories, transparency duties for chatbots, provider vs. deployer roles and a practical checklist for the AI features in your app.

6 min read
Legal, Privacy & SecurityAvoiding App Store Rejection: Common Reasons and Fixes

Avoid app store rejection: the most common reasons at Apple and Google Play, how to respond correctly and a pre-submission checklist to prevent rejections.

6 min read
Legal, Privacy & SecurityGDPR-Compliant App Development: The 2026 Checklist

GDPR-compliant app development: a practical checklist from concept and SDK selection to operations, so data protection never becomes costly retrofitting.

6 min read
Legal, Privacy & SecurityLegal Notice, Privacy Policy and Terms in Your App: A Guide

Legal notice (Impressum), privacy policy and terms in your app: which disclosures German law requires, where they belong and how to integrate them cleanly.

6 min read
Legal, Privacy & SecurityTracking Consent in Apps: What Germany's TDDDG Requires

Tracking consent in apps under Germany's TDDDG: when you need consent, what a compliant consent dialogue looks like and how to start SDKs correctly.

6 min read
Legal, Privacy & SecurityData Processing Agreements (DPA) for App Development and Hosting

DPAs for app development and hosting: when you need a data processing agreement, what it must contain and how to review providers and sub-processors properly.

6 min read