• Checked: 21–23 October 2026
• Versions: React Native 0.88.0
• Devices: iPhone, iOS 27; Samsung phone, Android 16; iOS 27.0 Simulator; Android 17 emulator
• Upstream: react/react-native#59377 and more

How It Was Checked​

• The source of every component exported from react-native was read on main (October 2026) for the props it passes to the native view; the device checks used 0.88.0. Not covered: the deprecated components, SafeAreaView, InputAccessoryView, VirtualView.
• The rows users hit were run in pairs, the aria-* prop next to its accessibility* form: on the Simulator and the emulator in the reproducer, read with Accessibility Inspector and uiautomator dump; View and Text with VoiceOver and TalkBack on phones in Memo Lab.

Result​

How a prop gets to the native side: each JS component converts aria-* to accessibility* itself (View, Text, TextInput, Image). The native side reads only the accessibility* names and role, so a prop the component does not convert is dropped.

• Pressable, Button, KeyboardAvoidingView, ImageBackground and the lists render a View, ScrollView or Image and have the same gaps.
• Not every gap matters: aria-modal on an Image or aria-live on a Switch make no sense. The ones that do: aria-label on Switch, role on Touchable*, aria-label on TouchableWithoutFeedback.
• aria-labelledby is a space-separated list of ids on the web; View splits it by commas, TextInput and Image pass it as one id, and Android uses only the first one. A web-style aria-labelledby="title hint" matches nothing.
• What works instead: the accessibility* form (accessibilityLabel, accessibilityRole, accessibilityState, accessibilityLiveRegion, accessibilityViewIsModal). Two exceptions: a live region on a View also needs collapsable={false}, and ActivityIndicator on iOS ignores even accessibilityLabel.

Upstream​

• react/react-native#59377: the issue with the whole table.
• Landed in main, not in a release on 27 October 2026: #59328 (aria-modal on View), #59330 (aria-live on Text), #59335 (a View live region).
• Open on 27 October 2026: #59378 (Touchable*), #59379 (Switch, ScrollView, ActivityIndicator), #59072 (aria-hidden on ScrollView and ActivityIndicator), #58173 (aria-labelledby on Button and Touchable*); #59380 and its fix #59381 (ActivityIndicator label on iOS).

• Checked: 22–23 October 2026
• Versions: React Native 0.88.0
• Devices: iOS 27.0 Simulator (Accessibility Inspector); Android 17 emulator
• Upstream: react/react-native#59380, fix #59381: open

How It Was Checked​

The indicator D in the reproducer, read with Accessibility Inspector:

<ActivityIndicator accessibilityLabel="Loading D" />

Result​

• With accessible the label is read, but the indicator's value is lost.
• On Android 17 the label is used: content-desc="Loading D".
• The cause: the accessibility props go to the wrapper view, VoiceOver skips it and reads the inner UIActivityIndicatorView. Switch solves the same case by exposing the inner native view as the accessibility element.

Upstream​

react/react-native#59380 is the issue, react/react-native#59381 the fix; it was checked on the Simulator with React Native built from source (the label is used and the value kept). Open on 27 October 2026.

• Checked: 22–23 October 2026
• Versions: React Native 0.88.0
• Devices: iOS 27.0 Simulator (Accessibility Inspector), Android 17 emulator (uiautomator dump)
• Upstream: react/react-native#59379: open

How It Was Checked​

Pairs in the reproducer: the left element uses the aria-* prop, the right one its accessibility* form. The accessibility tree was read without a screen reader.

<>
  <Switch aria-label="Wi-Fi A" value={on} onValueChange={setOn} />
  <Switch accessibilityLabel="Wi-Fi B" value={on} onValueChange={setOn} />
</>

Result​

• The cause: View, Text, TextInput and Image convert aria-* to accessibility* in JS. Switch, ScrollView and ActivityIndicator render a native component directly and convert nothing. RefreshControl and Modal do the same (read from the code, not run).
• On iOS a ScrollView is not an accessibility element, so a label does not apply there; ActivityIndicator on iOS ignores even accessibilityLabel, see a separate note.
• What works: the accessibility* form of the same prop.

Upstream​

• react/react-native#59377: the issue for all components.
• react/react-native#59379 adds the conversion to the three components; open on 27 October 2026.
• react/react-native#59072 maps only aria-hidden on ScrollView and ActivityIndicator; open on 27 October 2026.

• Checked: 21 October 2026
• Versions: React Native 0.88, Expo SDK 58
• Devices: Samsung phone, Android 16; Android 17 emulator
• Upstream: expo/expo#52032: open

How It Was Checked​

The keyboard-avoiding-view case of Memo Lab: a screen under a navigation header with a KeyboardAvoidingView and an input at the bottom; switches set behavior (none, padding, height) and keyboardVerticalOffset (0 or the header height). For each combination: tap the input, type, and look where the input is.

<KeyboardAvoidingView
  style={{ flex: 1 }}
  behavior={behavior} // undefined, 'padding' or 'height'
  keyboardVerticalOffset={withOffset ? headerHeight : 0}
>
  <View style={{ flex: 1 }} />
  <TextInput placeholder="Message" />
</KeyboardAvoidingView>

Result​

• The window keeps its height when the keyboard opens: the keyboard comes as an inset, not as a smaller window.
• The old reason to skip behavior on Android was that the window shrank by itself (adjustResize) and padding added a second gap. With edge-to-edge it does not shrink, so padding is right on both platforms.
• react-native-keyboard-controller behaved the same on both Android versions.
• This note covers Android only: on iOS the guide already sets padding.

Upstream​

expo/expo#52032 changes the guide's example to behavior="padding" on both platforms; open on 27 October 2026. A minimal Expo Go app for it: expo-kav-edge-to-edge.

• Checked: 21 October 2026
• Versions: React Native 0.88.0, Expo SDK 58 (development build)
• Devices: Samsung phone (SM-A276B), Android 16, TalkBack
• Upstream: react/react-native#59330: merged into main

How It Was Checked​

The announcements case of Memo Lab: counters in live regions, each changed by its own button; activate a button and wait for the announcement.

<>
  {/* A: silent */}
  <Text aria-live="polite">Cart A: {countA} items</Text>
  {/* B: announced on every change */}
  <Text accessibilityLiveRegion="polite">Cart B: {countB} items</Text>
</>

Result​

• A is never announced, B is.
• The cause: Text passes aria-live to the native side under that name, and the native side reads only accessibilityLiveRegion.
• Not affected: iOS, which has no live regions; there the app posts an announcement with AccessibilityInfo.announceForAccessibility.

Upstream​

react/react-native#59330 maps aria-live to accessibilityLiveRegion in Text. It was merged into main on 22 October 2026, after the 0.88 branch was cut; on 27 October 2026 it is not in a release (0.88.1 does not include it).

• Checked: 22–23 October 2026
• Versions: React Native 0.88.0
• Devices: iOS 27.0 Simulator (Accessibility Inspector), Android 17 emulator (uiautomator dump)
• Upstream: react/react-native#59378: open

How It Was Checked​

Pairs in the reproducer, the aria-* or role prop next to its accessibility* form:

<>
  <TouchableOpacity role="button" onPress={save}>
    <Text>Save G</Text>
  </TouchableOpacity>
  <TouchableOpacity accessibilityRole="button" onPress={save}>
    <Text>Save H</Text>
  </TouchableOpacity>
</>

Result​

With the accessibility* form each of them is right: android.widget.Button and the Button trait, the label "Close J", checked="true".

• TouchableNativeFeedback drops role too (read from the code, not run).
• aria-labelledby is dropped by all four (read from the code).
• Pressable does not have these gaps: it passes its props on to a View.

Upstream​

• react/react-native#59378 passes role from all four and maps the missing aria-*; open on 27 October 2026.
• react/react-native#58173 passes aria-labelledby through Button and Touchable*; open on 27 October 2026.

• Checked: 21 October 2026
• Versions: React Native 0.88.0, Expo SDK 58 (development build)
• Devices: iPhone, iOS 27, VoiceOver
• Upstream: react/react-native#59328: landed in main

How It Was Checked​

The modal case of Memo Lab: a screen with three background buttons and a custom overlay that is their sibling. With the dialog open, swipe right through all elements, then touch where a background button is.

<View style={{ flex: 1 }}>
  <View style={{ flex: 1, padding: 48, gap: 16 }}>
    {['One', 'Two', 'Three'].map((title) => (
      <Pressable key={title} role="button">
        <Text>Background item {title}</Text>
      </Pressable>
    ))}
  </View>
  <View
    aria-modal // or accessibilityViewIsModal
    style={{ position: 'absolute', inset: 0, justifyContent: 'center' }}
  >
    <Text role="heading">Dialog</Text>
    <Pressable role="button" onPress={close}>
      <Text>Close</Text>
    </Pressable>
  </View>
</View>

Result​

• aria-modal: swiping goes past "Close" to the background buttons, and touching them focuses them.
• accessibilityViewIsModal: focus stays inside the dialog.
• The cause: View converts the other aria-* props to accessibility*, but not aria-modal, and the native side reads only accessibilityViewIsModal. Pressable and Touchable* do map it.
• Not affected: Android has no modal prop at all, there the background is hidden with aria-hidden (importantForAccessibility="no-hide-descendants").

Upstream​

react/react-native#59328 maps aria-modal to accessibilityViewIsModal in View. It landed in main on 23 October 2026; on 27 October 2026 it is not in a release (0.88.1 does not include it).

• Checked: 21 October 2026
• Versions: React Native 0.88.0, Expo SDK 58 (development build)
• Devices: Samsung phone (SM-A276B), Android 16, TalkBack
• Upstream: react/react-native#59329, fix #59335: landed in main

How It Was Checked​

The announcements case of Memo Lab: counters in live regions, each changed by its own button; activate a button and wait for the announcement. Later the reproducer (plain React Native CLI, counters that change by themselves) showed the same, and was used to check the fix with React Native built from source.

<>
  {/* Silent: the View is flattened */}
  <View aria-live="polite">
    <Text>Cart: {count} items</Text>
  </View>
  {/* Announced */}
  <View aria-live="polite" collapsable={false}>
    <Text>Cart: {count} items</Text>
  </View>
</>

Result​

• Without collapsable={false} the counter is not announced, with it it is. View converts aria-live to accessibilityLiveRegion, so a View with accessibilityLiveRegion is flattened the same way (read from the code).
• The cause: Fabric keeps a host view for accessibilityViewIsModal, accessibilityElementsHidden and importantForAccessibility, but not for a live region. A live region is announced without the view being accessible, so it needs a view of its own.
• A View with a background color, a border, opacity, a transform, testID or nativeID is kept anyway, which is why a quick test often does not show the problem. Layout styles such as padding or flexDirection do not keep it.

Upstream​

react/react-native#59335 keeps a View that is a live region. It landed in main on 23 October 2026; on 27 October 2026 it is not in a release (0.88.1 does not include it).