[ryanbr]

Addresses the inline case of #571. Tools-only Python, so unlike the recent app-target PRs it's fully tested here — 26/26 and --ci clean, no verification gap.

The gap

#558 taught the audit to see conditional literals (Text(if x "a" else "b")), but a UI-text kwarg assigned inside a lambda stayed invisible. contentDescription is already in ANDROID_KWARG_PATTERN, but that pass is gated on an argument boundary (( or ,), so the standard Compose idiom

Modifier.semantics { contentDescription = if (hr) "Ready" else "No data" }

is skipped — its { isn't an arg boundary — and the audit reports clean while TalkBack reads English regardless of device language.

The fix

A dedicated assignment pass (ANDROID_A11Y_ASSIGN_PATTERN): a bare contentDescription = — not a == comparison, a .member read, or a val/var local declaration — is a UI-text site wherever it's assigned. It reads only its own value span via _argument_span_end (which stops at the enclosing }), so it does not reopen unrelated slot lambdas. The 489-explosion guard from #558 still holds (there's a test for exactly that).

Surfaces 22 pre-existing hardcoded a11y strings across 9 screens (AppRoot, CoachScreen, FusedRecordScreen, HealthScreen, PipBar, SettingsScreen, StepsCalibrationScreen, UpdatesInboxScreen, WorkoutsScreen) — all contentDescription = "literal" / = if … forms. Per the #558 pattern these land in the baseline as tracked backlog (170 → 192 android), not 22 rushed translations; --ci stays green and a genuinely new hardcoded literal still fails the gate.

Known limitation — val-laundered a11y is still NOT caught (correction to my first draft)

On re-review I confirmed this does not catch the specific case #571 cited as motivation. CoupledScreen.kt uses:

val a11y = when { … "Recovery calibrating, …" … else -> "Recovery, no data yet" }   // line 276
…
.semantics { contentDescription = a11y }                                           // line 305

The assignment's value is the variable a11y, so my pass finds no literal there; the literals live in the val a11y = when { … } declaration, which is deliberately not scanned (the #558 local-decl exclusion, there to avoid flagging a val text = when{} that isn't UI). Catching this needs light dataflow — "scan a val whose value flows into a contentDescription" — which is a distinct, more false-positive-prone change. So CoupledScreen's a11y strings remain invisible after this PR, and I'd keep #571 open (or spin a narrower follow-up) for the val-laundered variant rather than have this close it.

A few of the 22 are pure-interpolation ("$label: $valueText") that may need no translation — the baseline is a snapshot to triage, not a mandate.

Verification

• python3 -m unittest test_i18n_audit → 26/26 (4 new: the semantics idiom, multi-line, decl/member-read exclusion, the no-reopen-unrelated-slot guard)
• python3 Tools/i18n_audit.py --ci origin/main → exit 0