Maxim Malisciuc

AUTHADA GmbH, Senior Android Developer

I am a Software Developer with over 10 years of experience, primarily as an Android Developer. Along the way, I've also worked with Flutter, Kotlin Multiplatform (KMP), and various other technologies—whatever gets the job done. I'm a regular attendee of Droidcon Berlin 🤖 and passionate about sharing knowledge. I strive to make my talks engaging, insightful, and easy to digest, ensuring they provide real value without feeling overwhelming. Beyond speaking, I’ve published several articles and developed three apps that are actively helping doctors every day. I consider myself easygoing, but that doesn’t mean I lack expertise—I simply believe learning and sharing should be enjoyable.

Navigating the Roadblocks to European Accessibility Act (EAA) Compliance

TLDR; What will you learn: - Why focus on Accessibility? - What's EAA and why it is so messy? - Examples and Lessons learned - How hackers may exploit Accessibility services - How to make the Top App Bar accessible I'll try to add a permissible dosage of memes to make the leaning more comfortable. TLDR; is over! EU Parliament voted that all apps until 28 June 2025 should be compliant with Accessibility Act. (*+5 years transition *kind of*) Many of you are already deep into this process, so in this talk, I’ll focus less on the basics and more on real-world examples and solutions, which I will back up by specific success criteria and legislation within the EAA. Over the past year, I’ve been working intensively to bring my company’s legacy app into compliance. It’s been a deep dive into regulations, guidelines, and scattered resources - a true rabbit hole. The lack of clear, practical guidance makes accessibility compliance both time-consuming and complex. In this talk, I’ll walk you through our journey -highlighting the unexpected challenges, non-intuitive pitfalls, and hard-earned lessons along the way. I’ll also share a surprising statistic that might help you advocate for accessibility when speaking to stakeholders or decision-makers. My goal is to save you weeks of research by giving you practical tips and simple rules and solutions that can get your app 90%+ of the way toward compliance. And maybe, just maybe, I can plant a small seed - one that encourages developers to think more often about people with disabilities, and to make every ticket, every commit, just a little more inclusive.

Android Accessibility in Practice: Let’s Audit Your App

Accessibility on Android isn’t just good UX—it’s now a legal obligation under the European Accessibility Act (EAA). But real compliance goes well beyond passing an automated scanner. In this roundtable, we’ll roll up our sleeves and dig into what EAA compliance looks like in practice for Android developers. We’ll discuss how TalkBack interacts with real UIs, how to properly support font scaling and alternative navigation methods, and why screen orientation and motion sensitivity matter more than you think. Bring your accessibility questions, code samples, or current blockers—whether you’re just starting out or gearing up for an audit. We’ll share tools, techniques, and lived lessons for making apps more inclusive and compliant across Compose, Views, and hybrid setups. How are you currently testing for accessibility—do you rely on tools, manual testing, or both? What’s been the most confusing or surprising part of implementing EAA-related requirements in your Android app? Have you faced challenges making custom components accessible, especially in Jetpack Compose? How do you handle edge cases like font scaling, display size changes, or alternative input methods (e.g., Switch Access, keyboard, Voice Access)? What workflows or team practices help ensure accessibility isn’t an afterthought—but baked in from the start?