🏆And the winner is… On Friday, we celebrated the Kotlin community members who inspire, teach, build, and bring people together. Congrats to the winners! 👏 @matheuslf.dev, @skydoves.bsky.social, @nicole-terc.bsky.social. Eeva-Jonna Panula @eevis.codes, Yinlong Liu https://kotlinconf.com/awards/

Issue #6 of Inclusive Android Apps is live! 🚀 This one's about gendered language in period trackers — and how a few string changes and a dropdown can make your app welcoming for everyone who menstruates. Code included. Read it: buttondown.com/inclusive-an... #AndroidDev #InclusiveAndroidApps

Issue #6 of Inclusive Android Apps drops Tuesday! 📬 Topic: Gendered language in period tracking apps. Why assumptions about who menstruates exclude users, and how to fix it with inclusive string resources and code. Subscribe: eevis.codes/newsletter #AndroidDev #InclusiveDesign #MenstrualHealth

OK, I sent out jetc.dev Newsletter Issue #313! Bottom tab navigation! @eevis.codes on focus indicators! Hotkey DSL! Syntax highlighting! jetc.dev/issues/313 #JetpackCompose #AndroidDev

Android's default focus indicator is a ripple so subtle it's almost invisible, and that's a problem for keyboard and D-pad users. I wrote about building a custom one with the Indication API in Jetpack Compose: eevis.codes/blog/2026-04... #AndroidDev #a11y #JetpackCompose

I pushed the button on jetc.dev Newsletter Issue #311! @landomen.bsky.social on ViewModel Scope in Nav3! @eevis.codes on more inclusive drag-and-drop! Shared element transitions in Nav3! Official skills! jetc.dev/issues/311 #JetpackCompose #AndroidDev

Issue #5 of Inclusive Android Apps is live! 🚀 This one covers drag-and-drop and accessibility: why the pattern needs alternatives, and how to build them with buttons, keyboard support, and screen reader enhancements. Code included. Read it: buttondown.com/inclusive-an... #AndroidDev

Issue #5 of Inclusive Android Apps drops Tuesday 📬 This one tackles drag and drop: why it excludes users who can't perform the gesture, and how to build accessible alternatives with buttons and keyboard support, code included. Subscribe to get it in your inbox: eevis.codes/newsletter #AndroidDev

Issue #4 of Inclusive Android Apps is live! 🚀 This one tackles time-based actions: why they exclude users who need more time, and how to support Android's "Time to Take Action" accessibility setting, with code examples. Read it: buttondown.com/inclusive-an... #AndroidDev #InclusiveAndroidApps

Issue #4 of Inclusive Android Apps drops Tuesday 📬 This one is about time-based actions, why they might exclude users who need more time, and how to support the "Time to Take Action" accessibility setting, with code included. Subscribe to get it in your inbox: eevis.codes/newsletter #AndroidDev

Following up on my last post about building an item previewer in Jetpack Compose, I’ve published Part 2: Adding navigation support, in which I look into keyboard, screen reader, and voice access navigation considerations for the item previewer. eevis.codes/blog/2026-02... #A11y #AndroidDev

Eeva-Jonna @eevis.codes Panula on kaikkien aikojen ensimmäinen Mimmit koodaa -palkinnon voittaja. Tänä vuonna ympyrä sulkeutuu, kun hän on mukana tuomaristossa valitsemassa tulevaa voittajaa. Kysyimme Eeviksen kuulumisia, lue lisää ohesta. ☺️ #MimmitKoodaa

I released jetc.dev Newsletter Issue #302! Compose patch release and alpha release! Compose Multiplatform patch release! Bottom sheets! @eevis.codes on colors and accessibility! And... can we work with Glance?!? jetc.dev/issues/302 #JetpackCompose #AndroidDev

Issue #3 of Inclusive Android Apps is live! 🚀 This one covers the problem of color-only indicators: why relying on color alone excludes users, with code examples for fixing the issue with text, icons, and/or patterns. Read it: buttondown.com/inclusive-an... #AndroidDev #InclusiveAndroidApps

Issue #3 of Inclusive Android Apps drops Tuesday! 📬 This one's about color-only indicators: why relying on color alone excludes users, and how to fix it with text, icons, and patterns. Code included. Want to get it to your inbox? Subscribe here: eevis.codes/newsletter #AndroidDev

OK, I released jetc.dev Newsletter Issue #298! Compose Multiplatform 1.10! 🎉 Compose Hot Reload! @eevis.codes on bottom nav bar accessibility! Responsive tab rows! And... a no-Chromium desktop WebView?!? jetc.dev/issues/298 #JetpackCompose #AndroidDev

Looking back, I've mostly spoken at events abroad and in Turku, so I'm happy to share that I will be speaking at #ScanAgile26 in Helsinki in March! This time, my POV on accessibility is not the most technical, but how teams should value progress over perfection when fixing accessibility issues.

Font scaling is important, but what if UI elements can't scale? I’m borrowing a concept from iOS to build an item previewer in Jetpack Compose. It ensures small icons/labels stay accessible via item previews. Read more: eevis.codes/blog/2026-01... #A11y #AndroidDev

Issue #2 of Inclusive Android Apps is live! 🚀 This one tackles how to build gender forms that don't force binary choices. The practical solutions include multiple options, custom fields, and opt-out choices. Read it: buttondown.com/inclusive-an... #AndroidDev #InclusiveAndroidApps

Issue #2 of Inclusive Android Apps drops Tuesday 📬 This one's about gender selection in forms, why binary male/female choices exclude users, and how to build forms that actually work for everyone, with practical code examples. Want it in your inbox? Subscribe: eevis.codes/newsletter/ #AndroidDev

Compose-tip: When building reusable components, avoid unintentional nested clickable/selectable/toggleable elements, such as a `Column` with `clickable` that wraps a `Button`.

Compose (or Android) tip: Test your app with both button and gesture navigation to avoid breaking the user experience. When not testing with button navigation, it's easy to forget to leave enough padding for the buttons, which, in turn, can make some elements unusable at the bottom of the screen.

First issue of Inclusive Android Apps is live! 🚀 This one's about how Row layouts break when users increase text size - and why FlowRow is a good fix. Read it: buttondown.com/inclusive-an... #AndroidDev #AndroidAccessibility #a11y #InclusiveAndroidApps

Less than a week until the first issue of the Inclusive Android Apps newsletter! The response to the newsletter has been amazing, and I am so excited about it. I already have so many different ideas for the upcoming issues, and just can't wait to launch them! Did I already say I'm excited?

Compose tip: When you create either custom toggleable and selectable components (like switches, checkboxes, or radio inputs), or when you associate said native components with their labels and wrap them with, for example, a `Row`, use `toggleable` and `selectable` modifiers instead of `clickable`.

Android and Compose tip: Don't set a fixed height to components unless it's absolutely necessary. And even then, double-check if it is actually required, and test with large font sizes, such as 200%.

I've been testing different AI tools for generating Android apps and running accessibility tests on them, and now I've finally written my wrap-up of those tests. In short, from an Android accessibility perspective, I don't believe AI will replace developers anytime soon.

So I'm launching a newsletter about Inclusive Android Apps in December! Inclusive Android Apps is a monthly newsletter about making Android apps more inclusive. I cover accessibility, LGBTQ+ inclusive design, internationalization, and other considerations for apps to not accidentally exclude users.

Another Android accessibility tip: if you have `indication=null` set to your interactive components, it's likely that you're preventing anyone relying physical keyboard or d-pad for navigation.  This is, of course, if you haven't implemented proper focus indicators, which don't include ripples.

Another Compose tip: If you use `clickable`-modifier, or for example, a Button-component, you don't need to add `focusable`-modifier to that component. If you do, the component gets added twice to tab order, meaning users using assistive technology for navigation would focus twice on that component.

My talk from droidcon London is out! I share about creative coding, and some examples of what it can be.There's also live coding with Jetpack Compose Canvas  🤩 And of course, there are some ghosts 👻 #AndroidDev #Android #Kotlin #Canvas

An Android (and Compose) tip: Use IconButton-component instead of building own, clickable component from an image with modifiers. The button works out of the box with different input methods (touch, keyboard, Switch access, screen reader etc.)

I had a nice chat with in Berlin, and here's the recording, in which we discuss Android community, accessibility, debugging focus issues on Android, and other things. Let me know what you think! #dcbln25 #droidcon #AndroidDev www.youtube.com/watch?v=FO83...

I sent out jetc.dev Newsletter Issue #288! Material3 Adaptive! Cahier! @eevis.codes on font scaling tests! Data tables! And... will Compose work remotely?!? jetc.dev/issues/288 #JetpackCompose #AndroidDev

While testing Android apps for a11y, the biggest problems I see are with larger font sizes. I'm also often asked for how to write automated tests for accessibility, so I wanted to share tips on testing large font size related problems. eevis.codes/blog/2025-10... #AndroidDev #AndroidAccessibility

Only a couple of days and I'll be in London, talking about Creative Coding! #dcldn25 youtube.com/shorts/b1qnt...

I gave a talk today at droidcon Berlin (It's All About Focus - and Accessibility) and promised to share a link to the blog post with code samples - here it is: eevis.codes/blog/2025-07... #dcbln #dcbln25

Lately, I've been learning about Wear OS development, and naturally, accessibility has been a part of that learning journey. In the blog post, I share my learnings from supporting Talkback to Magnification. eevis.codes/blog/2025-09... #AndroidDev #AndroidAccessibility #A11y

I've been blogging for a while, and there is a thing or two I've learned about making blog posts more accessible. In this post, I share some of those things, from sharing code as text (instead of an image) to considering adding a summary in the beginning of the post. eevis.codes/blog/2025-07...

I just sent out jetc.dev Newsletter Issue #273! Android Makers! @eevis.codes on accessibility focus *and* keyboard focus! FABs and FAMs! PWAs! jetc.dev/issues/273 #JetpackCompose #AndroidDev

I've seen so much confusion around focus in Compose (TalkBack and keyboard), so I wrote a blog post about their differences, how to make components focusable, move focus programmatically, and change the traversal order for both of them. eevis.codes/blog/2025-07... #JetpackCompose #AndroidDev #a11y

Check out this week's Top 7 featured posts on DEV! Insightful reads from @eevis.codes, and @liztormato.bsky.social, plus five other fantastic authors. #Android #AI #RakuLang #CyberSecurity #DevOps dev.to/devteam/top-...

The next AI tool I've tested for how accessible Android code it generates is Cursor. The accessibility issues I found were similar to ones I've found with Gemini and Junie. While these tests are already painting a picture, I'll do one more round before writing a summary. eevis.codes/blog/2025-06...

I'm continuing on the theme of "Do AI-tools create accesible code", and this time, I tested Junie from JetBrains. The results were pretty similar to those with Gemini before - both test apps I generated have accessibility issues. eevis.codes/blog/2025-05... #a11y #AndroidDev #Junie

After some exciting things taking a lot of time, I finally had the time to publish my newest blog post, in which I discuss the accessibility problems text truncation can create, if it's not done right. I also offer some solutions to these issues. eevis.codes/blog/2025-04...

I just published a new video: Draw a Planet with Jetpack Compose Canvas - Silent Coding!

I just published a new video: Draw Saturn with Jetpack Compose Canvas - Silent Coding!

I just published a new video: Animate Text Colors on Jetpack Compose Canvas - Silent Coding!

Does Gemini provide accessible Android code? 👀 I generated two apps with Gemini and tested how accessible the app is. Result: the first one had multiple issues and the second one had less. I'll test other tools for comparison, so stay tuned! eevis.codes/blog/2025-03... #a11y #AndroidDev #gemini

I might have found the "No ARIA is better than bad ARIA" of the Android world: "No contentDescription for non-graphical elements is better than bad contentDescription". Folks (and especially generative AI), having content description attached to a Button or Text is usually a bad idea.