SwiftUI: Adding accessibility identifiers to VStack

Question

The goal is to add accessibility identifiers to a VStack where the VStack, View1, and View2 have their own, separate accessibility identifiers set, like so:

Code Block            VStack {	// identifier a
             View1	// identifier b
             View2	// identifier c
          }

When trying to use .accessibilityIdentifier(identifier) with any SwiftUI Stack, the identifier is applied to everything inside the VStack and overrides any identifiers that View1 or View2 may have had.

The current workaround is to use a GroupBox Container View to wrap the VStack. It achieves the desired result of having different levels of accessibility identifiers but has the drawback of coming with some styling (adds padding).

Is there a better way to go about adding accessibility identifier to a container view?

See Example playground

2.7k

Posted by

sparta

Reply

Add a Comment

Answer 1

You can call the accessibilityElement modifier on the VStack to create a separate element for it:

Code Block VStack {
}
.accessibilityElement(children: .contain)
.accessibilityIdentifier(/* VStack identifier */)

Posted by

Frameworks Engineer

Unfortunately using .accessibilityElement(children: .contain) cause huge memory leak, more like memory flood, as Accessibility framework holds reference to view which in tern holds models and all the dependents. See: https://developer.apple.com/forums/thread/689078

Leak manifests not only in UITests but by any accessibility use, even accessing it via Accessibility Inspector or Voice Over. See issue described here: https://developer.apple.com/forums/thread/689078 and sample project to reproduce the problem: https://github.com/yuri-qualtie/MemoryLeaks

Is there another way to add accessibility identifier to a SwiftUI container without causing leaks?

—
sparta
Unfortunately using .accessibilityElement(children: .contain) cause huge memory leak, more like memory flood, as Accessibility framework holds view which in tern holds models and all the dependents. See: https://developer.apple.com/forums/thread/689078

Leak manifests not only in UITests but by any accessibility use, even accessing it via Accessibility Inspector or Voice Over. See issue described here: https://developer.apple.com/forums/thread/689078 and sample project to reproduce the problem: https://github.com/yuri-qualtie/MemoryLeaks

Is there another way to add accessibility identifier to a SwiftUI container without causing leaks?

—
sparta

Add a Comment

Answer 2

You can call the accessibilityElement modifier on the VStack to create a separate element for it:

Code Block VStack {
}
.accessibilityElement(children: .contain)
.accessibilityIdentifier(/* VStack identifier */)

Posted by

Frameworks Engineer

Unfortunately using .accessibilityElement(children: .contain) cause huge memory leak, more like memory flood, as Accessibility framework holds reference to view which in tern holds models and all the dependents. See: https://developer.apple.com/forums/thread/689078

Leak manifests not only in UITests but by any accessibility use, even accessing it via Accessibility Inspector or Voice Over. See issue described here: https://developer.apple.com/forums/thread/689078 and sample project to reproduce the problem: https://github.com/yuri-qualtie/MemoryLeaks

Is there another way to add accessibility identifier to a SwiftUI container without causing leaks?

—
sparta
Unfortunately using .accessibilityElement(children: .contain) cause huge memory leak, more like memory flood, as Accessibility framework holds view which in tern holds models and all the dependents. See: https://developer.apple.com/forums/thread/689078

Leak manifests not only in UITests but by any accessibility use, even accessing it via Accessibility Inspector or Voice Over. See issue described here: https://developer.apple.com/forums/thread/689078 and sample project to reproduce the problem: https://github.com/yuri-qualtie/MemoryLeaks

Is there another way to add accessibility identifier to a SwiftUI container without causing leaks?

—
sparta

Add a Comment

Answer 3

Works perfectly. Thank you!

Posted by

sparta

was working great until we noticed that our memory footprint grown from 45 Mb to 2.5 Gb and keeps growing if user is using accessibility features.

—
sparta

Add a Comment

Answer 4

Hey Sparta. Has the memory leak subject been resolved? Thanks for letting me know

Posted by

jmgawe

Add a Comment

SwiftUI: Adding accessibility identifiers to VStack

Accepted Reply

Replies