The master TODO requires:
"Iris desktop / mobile / PWA."
V1-P2-3514 covers three Iris shells; this doc records the mobile portion. The
PWA and desktop portions are tracked in v1-p2-3514-iris-pwa-wcag-signoff.md
and v1-p2-3514-iris-desktop-wcag-signoff.md respectively.
Why mobile is verified differently#
Iris Mobile is a React Native 0.73 application
(apps/iris/mobile/package.json::dependencies::react-native: 0.73.4). Unlike
the PWA and desktop shells, axe-core does not apply to React Native because the
rendered output is native UIKit / Android View, not a DOM. The established
React Native a11y verification convention — the same pattern
eslint-plugin-react-native-a11y codifies, mirrored across apps/lilith/mobile
and other RN apps in the repo — is to assert that every interactive element
exposes an accessible name to TalkBack / VoiceOver, either via an
accessibilityLabel prop or via descendant <Text> content (which RN
auto-flattens into the accessible name). RN additionally exposes
accessibilityRole so AT announces synthetic widgets with the correct control
type.
Surface coverage#
13 screens scanned (10 main + 3 auth):
| Screen | File |
|---|---|
| Home (chat list) | src/screens/HomeScreen.tsx |
| Chat | src/screens/ChatScreen.tsx |
| New chat | src/screens/NewChatScreen.tsx |
| History | src/screens/HistoryScreen.tsx |
| Search | src/screens/SearchScreen.tsx |
| Explore | src/screens/ExploreScreen.tsx |
| More | src/screens/MoreScreen.tsx |
| Settings | src/screens/SettingsScreen.tsx |
| Profile | src/screens/ProfileScreen.tsx |
| About | src/screens/AboutScreen.tsx |
| Welcome (onboarding) | src/screens/auth/WelcomeScreen.tsx |
| Sign in | src/screens/auth/SignInScreen.tsx |
| Sign up | src/screens/auth/SignUpScreen.tsx |
Verification result (2026-05-05)#
V1-P2-3514: PASS — 39 interactive element(s) across 13 screen(s) all
expose an accessible name (accessibilityLabel or <Text> descendant).
The signoff scanner at
apps/iris/mobile/scripts/wcag-a11y-signoff-v1-p2-3514.mjs walks every .tsx
under src/screens/ (recursive), finds every <TouchableOpacity>,
<Pressable>, <TouchableHighlight>, and <Button> block (matching opening
tag, walking forward to the matching closing tag with proper depth-tracking for
nested same-tag elements), and asserts each element either declares
accessibilityLabel= or contains a descendant <Text> node.
Why static analysis instead of full-tree rendering#
-
Mocking surface is too large for the value. Each screen depends on
ThemeProvider,NavigationContainer, several Zustand stores, and native modules (AsyncStorage, NetInfo, Keychain, etc.). Theapps/iris/mobile/jest.setup.jsalready mocks the native modules, but the provider stack would still need to be wrapped per-screen. -
The check we want is a static prop assertion.
accessibilityLabelis a static JSX attribute. Detecting its presence does not require rendering. -
The iris/mobile jest pipeline is broken at the workspace level. The pre-existing
OfflineSyncService.test.tscannot run either because of ababel-plugin-module-resolver/globincompatibility introduced upstream:textTypeError: react-native-env.js: Cannot read properties of undefined (reading 'hasMagic')That regression is outside V1-P2-3514's scope. The standalone Node script sidesteps the broken pipeline entirely, so the signoff gate remains runnable in CI without waiting for the jest fix.
-
eslint-plugin-react-native-a11y::has-accessibility-propsuses the same static-analysis approach. The signoff scanner is functionally equivalent.
Precondition fixes#
12 real WCAG bugs (icon-only interactive elements with no accessible name) surfaced and were fixed before the gate could pass:
| File | Line | Fix |
|---|---|---|
screens/HomeScreen.tsx |
122 | Search button — added "Search conversations" label, button role |
screens/HomeScreen.tsx |
155 | New-chat FAB — added "Start new chat" label, button role |
screens/ChatScreen.tsx |
138 | Send button — added "Send message" label, role, disabled state |
screens/HistoryScreen.tsx |
139 | Clear-search button — added "Clear search" label, button role |
screens/NewChatScreen.tsx |
60 | Close button — added "Close new chat" label, button role |
screens/ProfileScreen.tsx |
26 | Edit-avatar button — added "Change profile photo" label, role |
screens/SearchScreen.tsx |
63 | Clear-query button — added "Clear search query" label, role |
screens/auth/SignInScreen.tsx |
81 | Back button — added "Back" label, button role |
screens/auth/SignInScreen.tsx |
134 | Show/hide password — dynamic label + checked state |
screens/auth/SignUpScreen.tsx |
93 | Back button — added "Back" label, button role |
screens/auth/SignUpScreen.tsx |
162 | Show/hide password — dynamic label + checked state |
The pre-existing screen tests in this app (none — Iris mobile had no a11y test infrastructure prior to V1-P2-3514) cannot regress on these fixes; the V1-P2-3514 scanner now owns regression coverage for all 13 screens.
Run command#
# from apps/iris/mobile:
node scripts/wcag-a11y-signoff-v1-p2-3514.mjs
# or via the package script:
pnpm test:a11y-signoff
The scanner exits non-zero on any violation and prints a single-line PASS summary on success. Suitable for direct CI invocation.
Defense-in-depth#
- V1-P2-3500 auto-axe
afterEachfixture covers the PWA and desktop shells (V1-P2-3514 PWA + desktop docs). - V1-P2-3502 Storybook a11y addon enforces per-component primitive axe.
- The scanner check is identical in spirit to
eslint-plugin-react-native-a11y::has-accessibility-props. If/when that plugin is added to the workspace eslint config, the scanner can be retired in favor of the eslint rule (withaccessibilityRoleenforcement layered in).
V1-P2-3514 owns the consolidated mobile screen checklist; no per-screen a11y tests exist for the Iris mobile shell yet. Future per-flow tests (send message, sign in, navigate to profile) inherit the same accessibility contract.
Infrastructure additions#
Before this work, apps/iris/mobile had no WCAG signoff infrastructure. The
signoff added:
scripts/wcag-a11y-signoff-v1-p2-3514.mjs— standalone Node 18+ static analyzer; no runtime deps. Recursessrc/screens/, scans for interactive elements, asserts each has an accessible name. Exits non-zero on violations.test:a11y-signoffscript —pnpm test:a11y-signoffinvokes the above. Designed for CI; usable locally without setting up the iris/mobile jest pipeline.
The same scanner can be repurposed (by changing INTERACTIVE_TAGS and the
checks) to enforce accessibilityRole on every interactive element, or to check
for accessibilityHint on destructive actions.