d3ro-voice/docs/evidence/2026-11-04-mobile-runtime-a11y.md
Yun Chan 7fe49c437e chore: land in-progress workspace changes before 1.16.2
The tree carried uncommitted work from several areas (web push, mobile
screens, admin charts, test-hygiene cleanup, CI and map docs). It is landed
as one commit so the release pipeline can start from a clean tree; the
desktop transcript-correction behaviour shipped in the previous commit and
is unchanged here.
2026-11-05 21:58:44 +09:00

7.3 KiB

2026-11-04 mobile runtime and accessibility evidence

All times are KST. This report keeps source, Android runtime, automated accessibility inspection, and manual screen-reader proof separate. No app data was cleared, no package was uninstalled, no default input method was changed, and no notification or accessibility setting was intentionally changed.

Verdict

Gate Result Boundary
Current-source Android artifact PASS (E2E, not production) 1.16.1-e2e.20261104.1 / 2026110401, non-debuggable, arm64-v8a + x86_64. This is not a signed production AAB.
State-preserving install and launch PASS adb install -r on a Fold6 running Android 16 and an isolated API 34 AVD. Existing app data was retained.
Notifications screen PASS for the already-granted/registered state The physical-device flow opened Notifications and asserted its status, privacy, and recent-notification cards without pressing a permission action. It does not prove permission denial/request/acceptance or real FCM delivery.
Automated Android accessibility PARTIAL PASS App-owned actionable nodes inspected on Home and Login were named and at least 48dp. The ad slot exposed one unlabeled clickable SDK WebView. Font scale 2.0 and portrait/landscape scrolling were checked on the AVD.
Manual TalkBack NOT RUN TalkBack was installed but not enabled on the physical device. UIAutomator output is not screen-reader announcement, focus-order, or activation proof.
iOS / VoiceOver NOT AVAILABLE The host is Windows. No iOS simulator/device or VoiceOver proof is claimed.

Artifact, install, launch, and logs

Build and verification:

cd apps/mobile-rn/android
D3RO_VERSION_NAME=1.16.1-e2e.20261104.1
D3RO_VERSION_CODE=2026110401
gradlew.bat :app:assembleE2e -PreactNativeArchitectures=arm64-v8a,x86_64 --no-daemon

node scripts/ci/verify-android-artifact.mjs \
  --apk apps/mobile-rn/android/app/build/outputs/apk/e2e/app-e2e.apk \
  --mode e2e \
  --expected-version-name 1.16.1-e2e.20261104.1 \
  --expected-version-code 2026110401 \
  --expected-admob-app-id ca-app-pub-3940256099942544~3347511713
  • Gradle: BUILD SUCCESSFUL, 644 tasks, about 3m42s.
  • APK: 147,160,979 bytes; SHA-256 3d2875c74b555dbcd854468e57b9b4b3a8e6c9657f210760cbe24a77ee92cf7c.
  • Verifier: package com.d3ro.voice, minSdk 24, targetSdk 36, debuggable:false, ABIs arm64-v8a/x86_64, test AdMob application ID, expected model hash, and signer inspection all passed.
  • adb install -r passed on both targets. The physical device retained firstInstallTime=2026-11-01 10:55:50; the AVD retained firstInstallTime=2026-11-01 10:32:43.
  • Cold am start -W completed in 185ms on the physical device and 1,024ms on the AVD. MainActivity became the resumed activity.
  • The inspected recent logcat window contained zero FATAL EXCEPTION, app AndroidRuntime process crash, or React fatal signature matches. This is a bounded window, not a long-duration ANR/privacy-log audit.

Notifications screen without permission mutation

The reusable flow is apps/mobile-rn/.maestro/notifications-permission-preserve-state.yaml. It launches with clearState:false, opens More → Notifications, and asserts these stable cards:

  • notification-status-card
  • notification-privacy-card
  • notification-recent-card

It contains no setPermissions, permission-button tap, app-data clear, or reinstall step. On the Fold6 it passed 1/1 in 30s. Local retained output is under apps/mobile-rn/.maestro-output/wave4-notifications-state-neutral-20261104/, including results.xml, the command trace, and artifacts/screenshots/notifications-status-preserved.png.

The rendered state was already Registered: Firebase configured, registration bound to the current device/account, privacy copy present, and no item received in the current session. This proves the screen and the current registered-state rendering; it does not prove transport delivery.

An earlier read showed POST_NOTIFICATIONS denied, while a later read showed it granted even though neither retained flow contains a permission request command. That transition cannot be attributed from the captured evidence. Therefore permission preservation across a denied-state run, the user-facing request/deny flow, and the Android system dialog remain open gates.

Automated accessibility inspection

The checks combined source inspection with uiautomator dump; they did not use TalkBack.

  • Physical Home at font scale 1.15: 16 clickable nodes, no target smaller than 48dp at the device's override density. Fifteen app-owned actions had a text or content description. The remaining clickable node was an android.webkit.WebView inside the banner ad slot.
  • API 34 AVD Login: all six actionable controls (Google sign-in, email, password, Sign in, Forgot password, Sign up) had labels and met the 48dp target. A focusable ScrollView was excluded because it is a container, not an action.
  • API 34 AVD at font scale 2.0: the portrait login controls remained reachable. In locked landscape, upward scrolling exposed password, Sign in, Forgot password, and Sign up. The AVD was restored to its prior font_scale=null, portrait rotation, and accelerometer setting after the check.
  • Source scan found accessibility attributes across the React Native surface, and focused Jest coverage passed for navigation, ScreenHeader, ads, and notification native/runtime paths. This is evidence for the inspected routes only, not an app-wide focus-order audit.

AdMob ownership boundary

The app-owned wrapper in FreeTierBanner.tsx has testID="free-tier-ad-slot" and the translated mobile.ads.sponsored accessibility label. The pinned react-native-google-mobile-ads@16.3.4 banner API explicitly does not forward standard View props; its BaseAd renders RNGoogleMobileAdsBannerView, and its Android manager creates the Google Mobile Ads SDK AdView, which supplies the observed WebView descendant.

Accordingly, the one unlabeled clickable WebView is an SDK-rendered descendant inside an app-owned labeled slot. The automated tree did not expose the wrapper label on that clickable descendant. Making the wrapper a single accessibility element could also hide or change activation of the SDK ad, so no behavior-changing workaround was applied without manual TalkBack proof. The announcement and activation behavior remains open.

Source gates run after the device check

Command Result
npm --prefix apps/mobile-rn run lint PASS, zero warnings/errors
npm --prefix apps/mobile-rn run typecheck PASS
Focused Jest: notifications, native/cold-start notifications, navigation shell, ScreenHeader, mobile ads 6 suites / 38 tests PASS

Open gates

  • Manual TalkBack announcements, traversal order, gesture activation, and the AdMob descendant behavior on a physical device.
  • Android notification permission deny/request/accept/system-settings transitions without resetting personal state.
  • Real foreground/background/terminated FCM delivery and notification deep-link receipt.
  • App-wide font-scale/rotation coverage beyond the inspected Login route.
  • iOS build/device, APNs receipt, dynamic type, and VoiceOver.
  • Signed production AAB, Play distribution, and production AdMob serving.