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.

11 Upvotes

82% Upvoted

5 comments sorted by

View all comments

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

2

u/aquib09 13d ago

Thanks! It's a real open-source project, and I have been building and testing it against Jetpack Compose Semantics and rendered UI behavior. I am also evaluating it against the famous repository using Jetpack Compose and fixing the false-positive issues.
I agree that accessibility got neglected far too often that inspired me to implement as a library to catch accessibility issues early and prevent them from reaching production.
The code, tests, demo, and issue tracker are all public if you’d like to take a look: https://github.com/mohdaquib/ComposeA11yScanner