European Accessibility Act and Barrierefreiheitsstärkungsgesetz

0 Comments

As the digital landscape evolves, it’s becoming increasingly essential for businesses to ensure their products and services are accessible to all users, including those with disabilities. Starting from June 28, 2025, companies providing (Android) apps will be required to meet accessibility standards. This article explores the underlying regulations, who they affect, the consequences of non-compliance, and why it’s crucial to start planning now.

New Accessibility Requirements for Apps

Beginning June 28, 2025, businesses that offer websites or apps must comply with accessibility requirements. This mandate aligns with the European Accessibility Act (EAA) and the German Barrierefreiheitsstärkungsgesetz (BFSG). The primary goal is to ensure that digital content and services are accessible to individuals with disabilities, thereby fostering inclusivity.

Underlying Regulations

The European Accessibility Act (EAA), implemented in German law through the Barrierefreiheitsstärkungsgesetz (BFSG), requires that digital products and services, including Android apps, adhere to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines cover various aspects of digital accessibility, such as:

  • Perceivable: Information and user interface components must be presentable to users in ways they can perceive.
  • Operable: User interface components and navigation must be operable.
  • Understandable: Information and the operation of the user interface must be understandable.
  • Robust: Content must be robust enough to be reliably interpreted by a wide variety of user agents, including assistive technologies.

Who is Affected?

The regulations apply to a wide range of businesses, including:

  • Companies developing and distributing apps in the European market.
  • Service providers whose services are primarily delivered through apps.

However, some small and micro enterprises may be exempt from certain requirements, depending on their size and scope of operations.

Consequences of Non-Compliance

Failing to comply with the accessibility requirements can lead to serious consequences, including:

  • Legal Penalties: Companies may face fines of up to 100.000€ and can even be forced to shut down their app business for not adhering to the regulations.
  • Reputation Damage: Non-compliance can result in negative publicity and harm a company’s reputation, affecting customer trust and loyalty.
  • Lost Opportunities: Businesses may miss out on a significant user base, as people with disabilities represent a considerable portion of the market.

As the law will only take effect next June, there have been no court rulings yet. In practice, it is likely that the government will initially adopt a lenient approach. However, there remains a significant risk of being sued by competitors for non-compliance.

Time to Start Planning

Given the impending deadline, businesses must start planning for compliance now. Six months can pass quickly, especially when balancing other important projects. Here’s a suggested approach:

  1. Audit Current Apps: Conduct an accessibility audit of your existing Android apps to identify areas needing improvement.
  2. Develop a Strategy: Create a comprehensive plan to address the identified issues, including timelines and resource allocation.
  3. Implement Changes: Begin making the necessary changes to your apps to meet WCAG 2.1 Level AA standards. Keep an up-to-date check-list of the required changes.
  4. Test and Iterate: Test the updated apps with real users, including those with disabilities, and iterate based on feedback.
  5. Educate Your Team: Ensure your development team understands accessibility principles and stays updated on best practices. Regularly re-visit WCAG 2.1 Level AA standards in test procedures to prevent accidental degradation.

By starting now, businesses can ensure they are ready to meet the accessibility requirements by the June 28, 2025 deadline, avoiding potential pitfalls and making their digital services accessible to all users.

Conclusion

The upcoming accessibility requirements for apps highlight the importance of inclusivity in the digital realm. By understanding the regulations, recognizing who they affect, and preparing for compliance, businesses can not only avoid legal repercussions but also contribute to a more inclusive and equitable digital world. Don’t wait—start your accessibility planning today!

If you are interested in more details about the Web Content Accessibility Guidelines, you can check out the NotebookLM Podcast. And if you are looking for support in that transition, drop me a message.

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts

Interviewing software engineers

Interviewing basics When interviewing software engineers, you typically want to answer one simple question: Will they be a good fit for my team? Therefore, your interviewing process should focus on answering this question. Obviously both sides try to answer…

Personal Jenkins Server with Docker

Nowadays, every software development team should have a continuous integration server like Jenkins. This is as true for Android developers as for any other platform. It makes sure the current source code compiles and all the…

Serverless on AWS Lambda

Serverless computing is a cloud-computing execution model in which the cloud provider dynamically manages the allocation of machine resources. At my current project, I had the freedom to create a new service a service from…