For games that share a common codebase with multiple targets, what would be the recommended way to handle accessibility? For example an iOS game with a WatchOS companion that can played standalone. Any word how Voice Control will affect this combination? For iOS 26, I've had to handle some aspects of accessibility separately and needed to separate out some of shared codebase into each target.
Our APIs are designed to work consistently across all of our platforms, so if you're using a shared codebase, using the same accessibility APIs should still provide the best experience on all the platforms you support!
Voice Control should not change things too much, although I'd recommend looking into accessibilityUserInputLabels to see how you can refine the experience for Voice Control. While Apple Watch does not support Voice Control, people can still use Voice Control with Apple Watch Mirroring, so adding userInputLabels to watch code will still help your users.
If you have specific questions about any specific interactions or experiences in your app, feel free to provide some examples and we'll try to provide some more specific guidance!
