[YevheniiKotyrlo]

Summary:

ScrollView and ActivityIndicator hand their props to a native component without the translation View gives aria-hidden, so the native side gets a prop it does not read and their content stays reachable by TalkBack and VoiceOver. #53364 closed the same gap for Text, TextInput and Image.

ScrollView now maps aria-hidden to importantForAccessibility="no-hide-descendants" and accessibilityElementsHidden the way TextInput and the touchables do. ActivityIndicator hands it, with accessibilityElementsHidden, to the View that wraps its indicator, so View's mapping decides both. On both components, aria-hidden={false} given with accessibilityElementsHidden={true} exposes the content, as it does on a View. RNTester's aria-hidden example gains a ScrollView and an ActivityIndicator.

Left out: Modal, whose content is shown in a window of its own rather than under its host view, and RefreshControl, which on Android wraps its scroll view, so aria-hidden on it would hide the scrolled content on Android but not on iOS.

#59379 overlaps this change: it maps aria-hidden on both components through a shared helper, together with the other aria-* props, and on Switch, which this change leaves alone. I'll close this one if #59379 is merged.

Changelog:

[GENERAL] [FIXED] - aria-hidden support for ScrollView and ActivityIndicator

Test Plan:

• Fantom: new cases in ScrollView-itest.js and ActivityIndicator-itest.js. Without the change, each component's case that sets aria-hidden and its case that removes it again fail; with it they pass, and so does yarn fantom as run_fantom_tests runs it (3284 tests). Run in reactnativecommunity/react-native-android:latest, the image build_fantom_runner uses.
• In the same image, the steps of the lint (yarn lint, yarn flow-check), test_js (245 suites), build_js_types, format, build_android and validate_cxx_api_snapshots jobs pass.
• Android: RNTester, APIs → Accessibility → aria-hidden, on an Android 16 emulator with TalkBack and aria-hidden on: touching the scroll view's text or the indicator moves TalkBack's focus onto it without the change, and leaves it where it was with the change.
• iOS: RNTester's Release build on an iPad with iOS 27.2, with a test screen in place of RNTester's root, its accessibility tree read through WebDriverAgent: without the change the text in a ScrollView with aria-hidden and an ActivityIndicator with aria-hidden are in the tree, with it neither is. RNTester's unit tests on the same iPad: the five that fail on main there, four RCTBundleURLProviderTests that expect a packager and RCTConvert_NSColorTests, fail the same way with the change, and no other test fails.

The TalkBack screenshots and the iOS accessibility-tree table are in the comment below.

[YevheniiKotyrlo]

Device evidence — before / after

UNFIXED — with aria-hidden on, touching the text in the ScrollView or the ActivityIndicator moves TalkBack's focus onto it.

FIXED — the focus stays on the switch it was on.

	before — main at f7cb270fba	after — with this PR
text in a hidden ScrollView
hidden ActivityIndicator

RNTester debug builds of main at f7cb270fba with the ScrollView and ActivityIndicator rows this PR adds to the aria-hidden example, without and with this change, on an Android 16 (API 36) emulator, 1140×2400 at density 480. With the example's aria-hidden switch on, TalkBack's focus is first put on that switch, and the screen is then touched at the scroll view's text or at the indicator through TalkBack's explore-by-touch: without the change the focus moves to the hidden element, with it the focus stays on the switch. A second run put the focus in the same place in every screenshot.

iOS — the accessibility tree, before / after

UNFIXED — the text in a ScrollView with aria-hidden and an ActivityIndicator with aria-hidden are in the accessibility tree.

FIXED — neither is, and with aria-hidden={false} and accessibilityElementsHidden={true} given together, both are in it, as on a View.

In the accessibility tree	before — main at b23e9a2677	after — with this PR
text in a ScrollView with aria-hidden	in	out
ActivityIndicator with aria-hidden	in	out
text in a ScrollView with aria-hidden={false} and accessibilityElementsHidden={true}	out	in
ActivityIndicator with aria-hidden={false} and accessibilityElementsHidden={true}	out	in

RNTester's Release build from a newer main than the Android pair's, b23e9a2677, without and with this change, on an iPad Pro (12.9-inch, 4th generation) with iOS 27.2, with a test screen holding these cases in place of RNTester's root; each tree is the hierarchy XCUITest reads, through WebDriverAgent's GET /source. On the same screen, text in a View with aria-hidden is out of the tree on both builds. accessibilityElementsHidden is iOS-only, so the last two rows have no Android counterpart. The test screen, the trees and the steps are in pr-59072, with the same screen built with #59379, which overlaps this change, and with #59381, which makes the UIActivityIndicatorView the accessibility element.

[YevheniiKotyrlo]

#59379, opened after this one, overlaps it: it maps aria-hidden on ScrollView and ActivityIndicator too, along with the other aria-* props, through a shared helper. I'll leave it to you which one to keep, and I'm happy to close this one if #59379 is merged.