How many of you found yourselves writing code, and making contentDescription = null? or contentDescription = "arrow button"? My hope is that after my talk you won't do that anymore! Or maybe you have to do that? EU Parliament voted that all apps until 28 June 2025 should be compliant with Accessibility Act. (*+5 years transition) -What is EAA? -Disabilities -WCAG 2.2 Guidelines -How to make your apps compliant? (It is not as easy as one might think) -Examples and lessons learned -Tricks that let you go beyond just content descriptions. For many months now I've been working on making my company's App compliant, and I had to do a lot of research. This subject is a rabbit hole, and finding clear concise information is not always easy, making it very time consuming, and complex. I will show you 1 screen that I made EAA compliant, and share with you challenges, and pitfalls that I did not estimate. My hope is that with this talk i can save countless weeks of research for other people, and give you a few rules, and tips, after applying which your Apps should already be 80%+ more compliant. Maybe I could plant a seed that would make developers think about people with special needs, and in each closed ticket make their App at least slightly more inclusive.