[Settings] Accessibility issues related to XAML Islands (RadioButtons control + null BoundingRectangle)

[alekhyareddy28]

ℹ Computer information

• PowerToys version:
• PowerToy Utility:
• Running PowerToys as Admin:
• Windows build number: [run "winver"]

📝 Provide detailed reproduction steps (if any)

• Run PowerToys Settings page.
• Run the Microsoft Accessibility insights app on PT Settings.

✔️ Expected result

What is the expected result of the above steps?

• No automated tests fail.
• We should tab into the selected radio button (in a group of radio buttons) and be able to navigate to the other radio buttons using the arrow keys. However, this does not happen when we add the radio buttons control in xaml islands.

❌ Actual result

What is the actual result of the above steps?

• It always tabs into the first radio button irrespective of which radio button in the group is selected.
• Navigation using arrow keys does not work, hence making the other radio buttons inaccessible using the keyboard.

Automated tests fail because of having the DesktopWindowXAMLSource Pane.

📷 Screenshots

More information can be found in this issue which fixes the tab related issue by using a stackpanel instead of a radiobuttons control - #5726

Corresponding issue in the microsoft-ui-xaml repo - microsoft/microsoft-ui-xaml#3156 (regarding the XYNavigation)

Corresponding narrator issue in the microsoft-ui-xaml repo - microsoft/microsoft-ui-xaml#3183 (regarding the narrator not reading the heading)

[alekhyareddy28]

This issue is due to xaml islands and would no longer exist when we shift to winui 3.

[alekhyareddy28]

@crutkas, I don't think we can solve it in this iteration. This issue is due to a pane being introduced by xaml islands, which does not have a property set. It is an internal pane and we cannot access it. I've added the winui-3 dependency tag. We should not have this issue anymore when we shift to winui-3. I think this should be removed from the milestone. I've created the above tracking issue (#6083) for issues which are dependent on the winui team to fix with links to issues in our repository. These issues are linked to the corresponding issue in the microsoft-ui-xaml repository.

[wayvad]

Hi @alekhyareddy28 , has the null BoundingRectangle accessibility issue (revealed by Accessibility Insight) been resolved? Thanks.

[niels9001]

We're not longer using RadioButtons group, so closing this issue

[DhananjaySaini007]

As per the comment, the Radio buttons are no longer used and UI has changed,
Hence, closing the bug.