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?
