At WeTransfer, we are building pure Compose apps, and recently one of our key initiatives was to make our apps accessible. Unfortunately, this initiative resulted in more refactoring than expected, even though our codebase is relatively new. In this talk, we’ll be discussing with real examples of what went wrong in the first place, how the old UI was constructed and what changes we had to make to make it accessible.

When we reflected on how this refactor made us rewrite some stuff, we decided to include accessibility as part of our development workflow. When we understood Talkback and Font scaling better, it gave us a new perspective on UI building. For Jetpack Compose, not just thinking in the state was helpful, but thinking in accessibility saved us from much technical debt.

Key takeaways
* The need to make our apps accessible
* Understanding the tools offered by Android for Accessibility
* Compose APIs for Accessibility
* Making custom views accessible
* Things that went wrong with our old Compose UI
* Accessibility as part of our UI building development workflow
* Building UI with Accessibility in mind


If you are curious and looking for what Jetpack Compose offers for accessibility, if you are looking to make your apps accessible and looking for a head start, or if you want to get prepared to make your app accessible soon, this talk is for you.