Given the new Voice Control natural language enhancements, is there any change in guidance for how developers use accessibilitylnputLabels? Does providing robust utterance coverage across our views still help tune the new system's NLU?
No change in guidance. It is still a best practice to provide accessibilitylnputLabels when the default label is sub optimal.
Your preferred label will be shown to the user as the recommended name when name labels are displayed, and input labels will be more performant than flexible names.
@Frameworks Engineer thanks. Is Apple Intelligence powered Voice Control generating its own set of input labels for all the elements in our view hierarchy? And if so, are these getting merged with the input labels we provide?
Is there a way to make it so that voice control can either use natural language to move X icon to folder XX now without having to use the number format? The reason I am asking is I would like to make it easier and make my first app for people with motor skills issues to be able to customize like you can on tvOS? I understand that I can recommend this feature but for now I would like to come up with an app and I wanted to know if I could use natural language and code to see if that would work. Thank you! Sincerely Donald Kirby a.k.a. Web webwolf27 or web wolf 2002 😊
