Evaluate accessibility with Accessibility Insights

[chrisglein]

• Test using voice input for text (Win+H)
• Test app using Narrator (Ctrl+Win+Enter to start, Caps+Space for scan mode)
• Implement headings (H/Shift+H)
  • Add support for UIA accessibility headings microsoft/react-native-windows#8516
• Implement landmarks (D/Shift+D)
  • [Accessibility] Add support for landmarks microsoft/react-native-windows#8452
  • Add support for UIA accessibility landmarks microsoft/react-native-windows#8708
• Fix mouse hover controls to be accessible on key focus. This is what Teams does, for example.
• WCAG 4.1.2: (artificialChat/group 'AI response') Focusable sibling elements must not have the same Name and LocalizedControlType. #95
• WCAG 4.1.2: (artificialChat/group 'AI response') Focusable sibling elements must not have the same Name and LocalizedControlType. #96
• WCAG 4.1.2: (artificialChat/group 'Human prompt') Focusable sibling elements must not have the same Name and LocalizedControlType. #97
• WCAG 4.1.2: (artificialChat/group 'Human prompt') Focusable sibling elements must not have the same Name and LocalizedControlType. #98
• Section 508 502.3.1: (artificialChat/text ' ') The Name property must not contain only space characters. #99

Summary

What WinUI Gallery looks like (what I assume to be an app in good standing):

What this app looks like:

[chrisglein]

• Should the icon be given role "none"? Or "image"?
• Unlike in WinUI2, the label for TextBoxes isn't included. Should it be grouped somehow?
• There are no groups like I see in gallery I don't see those in the valid roles list
• Should the prompt textbox be of role "search"?
• I've set things as role "header", but nothing changes
• The "edit" roles are TextInput, but the value doesn't seem to show through here. The placeholder value does. Is that correct?