[Android] TalkBack does not correctly narrate RadioButtons with Content

[KillswitchPrime]

Description

When using more advanced RadioButton functionality, like using the Content property, the Android TalkBack screenreader completely loses its ability to narrate the component.
Following this guide: RadioButton visual states leads to a broken screenreader.

Completely basic RadioButtons with no/empty Content property will work just as expected.

Steps to Reproduce

1. Turn on TalkBack in the Android Accessibility settings.
2. Open the repro app.
3. Have the screenreader narrate the different radio buttons to verify that they are not described correctly.

Link to public reproduction project repository

https://github.com/KillswitchPrime/MauiRadioButtonsAndroidA11y

Version with bug

10.0.20

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

Android

Affected platform versions

Pretty sure this will affect all Android versions.

Did you find any workaround?

Setting the property SemanticProperties.Description on the radio buttons helps a little, but the screenreader still does not tell the user what state the radio button is in, whether it is checked or unchecked.

Relevant log output

[LogishaSelvarajSF4525]

This issue has been validated in Visual Studio Code 1.109.5 with MAUI versions 9.0.0, 9.0.120, 10.0.20, 10.0.40 & 10.0.41. It can be reproducible on the Android platform. Here I attached the video for reference :

Screen.Recording.2026-03-04.at.5.33.50.PM.mov

Note: Group 1 worked because SemanticProperties.Description(workaround) is set for each RadioButton, but since it is not set in Group 2, the issue was reproduced there.

[KillswitchPrime]

This issue has been validated in Visual Studio Code 1.109.5 with MAUI versions 9.0.0, 9.0.120, 10.0.20, 10.0.40 & 10.0.41. It can be reproducible on the Android platform. Here I attached the video for reference :
Screen.Recording.2026-03-04.at.5.33.50.PM.mov

Note: Group 1 worked because SemanticProperties.Description(workaround) is set for each RadioButton, but since it is not set in Group 2, the issue was reproduced there.

I disagree with saying that Group 1 "works". It is better than Group 2, but the screenreader does not convey the status of the radio button. Is it selected? Is it unselected? If you are blind, it is impossible to know, because the screenreader does not tell you.