Solution FinderSolutions
  1. Home
  2. Situations
  3. Accessible app
Situation · Accessible app · Berlin & Germany-wide

The BFSG applies to your app too.We make it accessible.

Since 28 June 2025, Germany’s Accessibility Strengthening Act (BFSG) also covers mobile apps in consumer business. The benchmark is WCAG 2.1 level AA and EN 301 549 – we build it into the design instead of retrofitting it.

No obligation · 15 minutes · reply usually within 24 hours

01

The situation

Your app is aimed at consumers – for booking, ordering, buying or entering a contract. Since June 2025, customers, partners or your own legal team have been asking whether it’s accessible. And nobody on the team knows exactly what that means for an app.

Typical sign: contrast is too weak, buttons have no name for screen readers, errors are only marked in red, and the focus order jumps across the screen. Fixing such issues afterwards is tedious – which is why accessibility belongs in design and development, not in a retrofit.

02

Our solution

We build your app to WCAG 2.1 level AA and EN 301 549: sufficient contrast, full keyboard operability, a logical focus order, text alternatives, labelled form fields and clear error messages. We check every colour combination in the design system – 4.5:1 for body text, 3:1 for large text and controls – and states carry text or a symbol, not colour alone.

For apps covered by the BFSG, we review the relevant requirements and document the status. Design follows each platform’s conventions – iOS, Android or web – and the developer spec includes accessibility notes. We don’t replace legal advice; we implement the requirements.

App development in detail
03

Process & details

How your app becomes accessible:

  1. 01Understand
  2. 02Structure
  3. 03Design
  4. 04Test
  5. 05Finalise & hand over

Whether your offering falls under the BFSG is something our free BFSG check estimates in about two minutes – and it explicitly asks about apps too. For an existing app we start with a UX audit that includes accessibility criteria; for a new app, accessibility is part of the concept from day one.

Describe your app on WhatsApp

Companies working with KULIMO

Our clients, on the map

Every pin is a partnership. Hover the globe to see who we work with, and where.

4 clients worldwide

  • Adltortechnik

    Waiblingen, Germany

    ADL Tortechnik is a specialist company based in Waiblingen (Stuttgart region), focused on the planning, sale, installation and maintenance of modern door, gate and loading-bay technology.

    Visit site
  • Das Catering

    Germany

    Das Catering (Das Catering Berlin) is the full-service catering arm of the Berlin restaurant concept Die Stulle. Based at the same address in Berlin-Charlottenburg, the team caters private celebrations, brand events and corporate functions in Berlin and Brandenburg.

    Visit site
  • Die STULLE

    Berlin, Germany

    Visit site
  • WCAG 2.1 AA as standard
  • EN 301 549 as benchmark
  • Accessibility from the start
  • Contrast checked in the design system
  • Status documented
  • Design and development in one team
  • Owner-led studio in Berlin
What you get

This is what you get.

Every line is on our service page – nothing we don’t deliver.

  1. 01

    Accessible design

    Contrast, focus, keyboard use and WCAG 2.1 AA from the start – already considered in the prototype.

  2. 02

    Clean structure

    Heading hierarchy, labelled forms and text alternatives – a structure screen readers can rely on.

  3. 03

    Accessibility testing

    A test phase with an accessibility check and revisions before the app goes live.

  4. 04

    Developer spec

    Measurements, tokens, behaviour and accessibility notes – or direct implementation by KULIMO.

  5. 05

    Documented status

    For apps covered by the BFSG: relevant requirements reviewed, status documented.

Process

Four steps to the finish.

From the first call to the handover.

  1. 01

    Intro call

    15 minutes, free. App, audience, platforms and today’s state of accessibility.

  2. 02

    Audit or concept

    Existing app: UX audit with accessibility criteria. New app: requirements in the concept. Then a fixed quote.

  3. 03

    Design & development

    Contrast, focus, labels and error messages in the design system and code.

  4. 04

    Testing & documentation

    Accessibility check, revisions and a documented status.

Questions from search

Frequently asked questions

  • Does the BFSG apply to apps?

    Yes. The BFSG implements the European Accessibility Act and explicitly covers mobile apps and electronic services in consumer business, not only websites. Our BFSG check gives a first estimate of whether your offering is affected – not legal advice.

  • Which standard applies to accessible apps?

    The benchmark is WCAG 2.1 at conformance level AA, or the harmonised standard EN 301 549.

  • How do I build accessible apps with Flutter?

    The requirements are the same as for native apps: contrast, labelled controls and form fields, text alternatives, a logical focus order and clear error messages. We also build cross-platform with Flutter or React Native and plan accessibility in from the start.

  • Can an existing app be made accessible later?

    Yes. We start with a UX audit against accessibility criteria and prioritise the findings; in the process we check whether we can continue developing the existing code.

  • Do we get an accessibility certificate?

    We don’t certify. We implement WCAG 2.1 AA, review the relevant requirements and document the status – that doesn’t replace a legal assessment.