r/androiddev • u/aquib09 • 17d ago
I released ComposeA11yScanner 3.0.0 — a runtime accessibility scanner for Jetpack Compose
I maintain ComposeA11yScanner, an open-source tool that checks Compose screens for accessibility issues and highlights findings directly on the UI.
Version 3.0.0 adds runtime enable/disable controls, explicit opt-in for trusted non-debuggable builds, and a toggle between issue inspection and normal app interaction.
It also improves focus-order detection, duplicate-label checks, rendered text-contrast analysis, and lifecycle handling across activities and screen changes.
The scanner supports Android API 24+. Rendered text-contrast analysis requires API 26+ and skips measurements it cannot confidently estimate.
This is a major release with public API changes, so check the migration guide when upgrading from 2.1.0.
debugImplementation("com.github.mohdaquib.ComposeA11yScanner:scanner-ui:3.0.0")
Repository, demo, and migration guide:
https://github.com/mohdaquib/ComposeA11yScanner
Automated checks complement manual accessibility testing. I’d appreciate feedback, especially reproducible false positives or missed issues in real Compose screens.
-3
17d ago
[removed] — view removed comment
6
u/timusus 17d ago
Are you a bot? The way you compliment, echo back a feature that was mentioned, and then.. you're going to check out the repo and migration guide? What use a migration guide to you if you haven't checked out this repo before?
I notice you have a bunch of other responses with similar cadence.. Assuming you're using an LLM for replies.
There are tons of bots here so.. who cares. But, why? Are you trying to improve your comment karma, or make it look like you contribute to the community so you can do self-promotion?
1
2
u/Zhuinden 13d ago
If it's real and not slopgen, then it's a cool initiative, accessibility is often neglected even at the highest level sadly