The .accessibilityElement(children: ) modifier with the .ignore argument does a similar thing to set the container view to be an accessibility element in UIKit. It is the default argument, so you can just say .accessibilityElement().

Two instances of the Stock Analyzer app showing you what it is included with the pro version and how much it costs. The first one uses .accessibilityElement(children .combine) to group three elements, and that causes VoiceOver to announce

Because of this, you'll need to use other modifiers to make it accessible and manually configure an accessibility label and value, traits... when necessary.

https://developer.apple.com/documentation/swiftui/view/accessibilityelement(children:)

https://developer.apple.com/documentation/swiftui/accessibilitychildbehavior/ignore

You may also find interesting...

In UIKit you can create keyboard shortcuts by overriding the keyCommands for your view controller, which is an array of UIKeyCommand. A bit of a different approach to how you'd do it with SwiftUI.

Apple asks us to consider the combine behavior, before using ignore, for .accessibilityElement(children: ). And for good reason, if combine works, and later on you decide to change the UI, the accessibility attributes will be updated for you.

Support both orientations, if possible. I know not even iOS itself does it, but it hasn't always been like that. You'll create a more robust UI that will be easier to port to iPadOS. And especially, don't force your users to rotate their devices.

Created in Swift with Ignite.

Supporting Swift for Swifts