6 posts tagged with "Android"

Every core component accepts role and the aria-* props in its types, but in React Native 0.88 several components drop some of them without a warning, while the accessibility* form of the same prop works.

Switch, ScrollView and ActivityIndicator accept all View props in their types and docs, but in React Native 0.88 they pass aria-*, id and tabIndex to the native side unconverted, where nothing reads them. <Switch aria-label="Wi-Fi" /> has no name; accessibilityLabel works.

Expo's keyboard guide sets behavior={Platform.OS === 'ios' ? 'padding' : undefined}. An edge-to-edge app (every Expo SDK 54+ app on Android 16, and Android 15 enforces it for apps targeting API 35) does not shrink its window for the keyboard, so with no behavior the input stays under the keyboard. padding or height with the header offset keeps it right above the keyboard. Checked on Android 16 and 17.

Text accepts aria-live in its types, but in React Native 0.88 it does not convert it to accessibilityLiveRegion, as View does. A counter in <Text aria-live="polite"> is never announced by TalkBack; the same counter with accessibilityLiveRegion="polite" is announced on every change.

Touchable* build their native view from a fixed list of props, and in React Native 0.88 role is on none of the lists. <TouchableOpacity role="button"> has no role; accessibilityRole="button" works. TouchableWithoutFeedback also drops aria-label, and TouchableHighlight drops aria-checked and the other aria-* state props.

A View with aria-live or accessibilityLiveRegion and no style (or only layout styles) is removed from the native tree by view flattening in React Native 0.88, so the live region does not exist and TalkBack announces nothing. collapsable={false} keeps the view and the live region works.