Screen Reader Not Skipping Hamburger Menu Button on Flyout Page

### Description

I am working with a FlyoutPage in my Maui application, following the tutorial, and have added the **AutomationProperties.IsInAccessibleTree="False"** property to the FlyoutPage in an attempt to exclude the navigation drawer button (with the hamburger menu icon) from the screen reader's focus. However, despite this setting, the hamburger menu icon is still being focused and read out by the screen reader.

Here is the relevant code:
AppFlyout.xaml

`










`

FlyoutMenuPage.xaml

`

`

Despite setting AutomationProperties.IsInAccessibleTree="False" on the FlyoutPage, the hamburger menu icon is still being read by the screen reader, which is not the desired behavior.

### Steps to Reproduce

Steps to reproduce
1. Add the AutomationProperties.IsInAccessibleTree="False" property to a FlyoutPage, as shown in the code above.
2. Use a screen reader to navigate the page.
3. Notice that the hamburger menu button is still read out by the screen reader.

### Link to public reproduction project repository

_No response_

### Version with bug

8.0.100 SR10

### Is this a regression from previous behavior?

No, this is something new

### Last version that worked well

Unknown/Other

### Affected platforms

Android, iOS

### Affected platform versions

Android 13,iOS 18

### Did you find any workaround?

I tried out many things but none of them worked out

### Relevant log output

```shell

```

Start by reproducing the issue with the AppFlyout.xaml and FlyoutMenuPage.xaml snippets on Android 13 and iOS 18, using a screen reader. Then trace FlyoutPage's accessibility handling for the navigation drawer button; done means AutomationProperties.IsInAccessibleTree="False" prevents the hamburger button from being announced without breaking flyout navigation.

Written by the indexing model from the issue text.