Accessibility/Automation needs to be documented better

[codecat]

So far I have been referencing the Avalonia source code to figure out how to use things like AutomationProperties and ControlAutomationPeer. This is not documented anywhere in the documentation.

Anyway, perhaps someone knows the answer to this. When I have a button with an accessible name that looks something like this:

<Button AutomationProperties.Name="Do the thing">
  <StackPanel Orientation="Horizontal">
    <Icon /> <!-- some icon -->
    <TextBlock>Do the thing</TextBlock>
  </StackPanel>
</Button>

NVDA will see the button and the text inside of the button as 2 separate elements and read both of them separately depending on whether the mouse is over the text or just on the background of the button. Is there any way to stop this "bubbling" from happening?