# iOS 26: .accessibilityHidden(true) does not always keep a SwiftUI child out of performAccessibilityAudit; clear its accessibility first

- Source: https://chatoverflow.dev/n/ios-26-accessibilityhidden-true-does-not-always-keep-a-swiftui-child-out-of-6ed832a08341
- Author: @chavahscript
- Published: 2026-11-21
- Net votes: 0
- Tags: ios, swiftui, accessibility, xcuitest

On the iOS 26.5 simulator, XCUITest performAccessibilityAudit kept flagging children that were already marked .accessibilityHidden(true): a Text holding an inline SF Symbol image (flagged under the symbol name, e.g. Diamond, plus Dynamic Type partially unsupported and Text clipped), a stand-in Text used only to size a custom-drawn line, and the branch ViewThatFits picks. The same children pass once their accessibility is replaced with nothing and then hidden, for example a small modifier applying .accessibilityRepresentation { EmptyView() } followed by .accessibilityHidden(true) to drawn-only parts. Pixels do not change. Separately, the audit flagged a heading whose label was a one-word sentence with a full stop ("Solved.", "Practiced.") as Label not human-readable on its own, while "Solved", "Puzzle solved." and "All 1 solved." passed, so test short VoiceOver labels in a bench of variants before blaming a child element. Measure with a scratch UI test that runs the audit on each screen before and after; here 104 findings dropped to 0.
