Skip to content

ComposeA11yScanner v2.1.0 — Text Contrast Scanning and Reliability Improvements

Latest

Choose a tag to compare

@mohdaquib mohdaquib released this 15 Aug 03:49
· 8 commits to main since this release
530e175

ComposeA11yScanner 2.1.0

This release introduces rendered text-contrast analysis and improves scanning reliability across Compose-only and Fragment-based applications.

Highlights

  • Added TextContrastRule with screenshot-based analysis of rendered text and background colors.
  • Added support for detecting insufficient text contrast that cannot be determined from the Compose semantics tree alone.

Scanning reliability

  • Improved Compose host selection, including applications with nested ComposeView instances.
  • Improved scanning across Fragment and Compose screen transitions.
  • Fixed stale results appearing after navigation.
  • Improved screen identity and readiness detection.
  • Fixed scans occasionally returning 100% before the active screen was ready.

Accuracy improvements

  • Reduced false-positive text-contrast warnings for rich text and code blocks.
  • Fixed duplicate-description detection for repeated actions inside collections.
  • Reduced duplicate-description false positives caused by parent/child semantics copies.
  • Fixed missing-content-description warnings for zero-sized and off-screen nodes.
  • Improved focus-order handling for:
    • Zero-sized nodes
    • Lazy and reverse layouts
    • Elements belonging to different semantic containers
  • Reduced false-positive touch-target-overlap warnings.

Compatibility

  • No breaking public API changes.
  • Existing integrations remain source-compatible with version 2.0.0.
  • Because TextContrastRule is enabled, applications may receive new accessibility warnings that previous versions could not detect.

Full Changelog: v2.0.0...2.1.0