Accessibility Audit (Android)

Why this matters

Every ImageView, ImageButton, Image, Icon, and IconButton that conveys meaning needs an android:contentDescription (XML) or contentDescription = stringResource(...) (Compose). Without it:

• Users with vision impairments — TalkBack announces "image" or skips silently. The user cannot tell what the icon is for. They can't tap it confidently. Effectively, the feature doesn't exist for them.
• Automation tests — Espresso, UI Automator, Compose UI Test, MagicPod, BrowserStack App Live, and every other framework rely on accessibility labels as the primary way to find elements. onView(withContentDescription("Cart")) is the right way to write a cart-button assertion. Without labels, tests fall back to withId(R.id.cart_image) — brittle, breaks on any layout refactor.
• Compliance — WCAG 1.1.1 (Non-text Content), Section 508, AODA, EN 301 549. Missing labels are a direct fail.
• Voice control + Switch Access — Android's voice-control feature relies on contentDescription to know what the user means by "tap cart" — without labels, the user can't drive the app by voice.

Decision matrix — when to label, when to mark decorative

Audit findings

Missing contentDescription on actionable XML images

15 sites identified — each is an icon that does something on tap, with no announcement for assistive technology.

Empty / null contentDescription on actionable elements (anti-pattern)

Hardcoded font sizes — Dynamic Type / "Large Text" ignored

WCAG 1.4.4 requires text to scale up to 200%. The following sites hardcode android:textSize or Compose fontSize instead of using MaterialTheme.typography / ?attr/textAppearanceBody1. Users with the system "Large Text" setting see clipped, overlapping content.

Plus 30+ more sites across the codebase. Recommendation: sweep all hardcoded textSize values; replace with ?attr/textAppearanceHeadline6, textAppearanceBody1, etc., or with explicit Material/Material3 type tokens.

Hardcoded text strings — bypass localization + accessibility services

Hardcoded strings in XML are not picked up by translators, can't be intercepted by per-app language preferences (Android 13+), and break TalkBack's pronunciation in non-English locales. Sample (likely many more):

• row_media_card.xml:36 — "Auto Sales Event"
• view_warehouse_details.xml:140 — "Warehouse coming soon!"
• view_warehouse_comingsoon_details.xml:117 — "warehouse coming soon" (note inconsistent capitalization)
• list_item_nearby_warehouses.xml:102 — "Warehouse coming soon"
• view_warehouse_gas_comingsoon_details.xml:78 — "warehouse coming soon"

Hot files (most violations)

1. Costco/src/main/res/layout/view_warehouse_details.xml — 6 violations (3 missing img descriptions + 3 hardcoded fonts)
2. Costco/src/main/res/layout/fragment_onboarding.xml — 5 violations (all DYNAMIC_TYPE)
3. shared/geofence/.../layout_notification_collapsed.xml — 4 violations (all fonts)
4. Costco/src/main/res/layout/view_warehouse_comingsoon_details.xml — 4 violations (1 missing desc + 3 fonts)
5. Costco/src/main/res/layout/fragment_feature_highlights.xml — 4 violations (all fonts)

How fixing this helps automation

The same labels that announce intent to users are what automation frameworks use to find elements. After labeling:

The automation team can drop XPath/resource-id selectors entirely once labels exist. Tests stop breaking on every layout refactor. New features can ship UI tests without first wiring up resource IDs. Cross-platform tests (Appium, etc.) can use the same accessibility ID on Android and iOS — your labels become a stable contract.

Migration plan

1. Sprint 1 — Add android:contentDescription to the 15 actionable XML icons. Each goes via a string resource so localization picks it up. Sweepable in 1 day.
2. Sprint 1 — Replace contentDescription="" and incorrect "@null" with proper resource strings or android:importantForAccessibility="no".
3. Sprint 2 — Sweep hardcoded android:textSize values; convert to text-appearance attributes. Snapshot test at fontScale = 2.0.
4. Sprint 2 — Sweep hardcoded UI strings into strings.xml.
5. Ongoing — Enable Android Lint rule ContentDescription at error severity in CI. Enable HardcodedText rule. Re-baseline.
6. Ongoing — Add a fontScale = 2.0 snapshot test pass in the existing screenshot test plan.

Verification

• Manual TalkBack pass — turn TalkBack on, navigate Home → Warehouse Detail → Offers. Every actionable element should announce its purpose.
• Accessibility Scanner app (free, Google) — scan key screens, fix flagged sites until count reaches zero on critical screens.
• Lint baseline — ContentDescription rule should report 0 new findings on any PR.
• UI test coverage gain — pick one feature and rewrite its UI test to use withContentDescription instead of resource IDs; verify it survives a layout refactor.