Another year, another WeCoded-post. This time it's about feeling invisible, being told my existence is propaganda, and some assumptions of incompetence.
When enabling font scaling is not an option, the iOS-like large content viewer functionality can be an answer. But you need to support assistive technology with it as well.
What if enabling font scaling is not an option for some element, like the bottom bar? One option would be to build iOS-like large content viewer functionality.
I was fixing an Android app and found buttons in a row getting cut off when I increased the font size. After diving into the code, the problem became clear: it was using `Row` when `FlowRow` was needed.
I’m often asked tips on writing accessibility tests for Android, and I decided to write this post to demonstrate how to test some issues with larger font sizes with UI tests.
This is a living document about how to work with me, and I try to update it when I learn or realize something new. I didn't want to create a dedicated page for it, at least not just yet, so I published it as a blog post.