You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When narrator is launched and we tab in and out of xaml content island narrator doesn't recognize the element and announce the accessibility properties.
Adding on to what the issue is:
observed an accessibility issue when navigating XAML controls hosted inside a ContentIsland in React Native Windows with Narrator enabled. Keyboard focus works correctly: Tab navigation moves focus to the XAML control, and keyboard interaction behaves as expected. The problem is not focus navigation.
The issue is with UI Automation focus. When focus moves into a XAML island, RNW raises the UI Automation focus event on the ContentIsland (container) instead of the XAML control. Since Narrator follows UI Automation focus (not keyboard focus directly), it announces the container (“Pane”) rather than the actual control.
Verified that XAML already provides correct accessibility and that overriding or creating automation peers is not required.
This confirms the problem is framework-level, specifically in the UI Automation focus event path.
The intended design is that ContentIslandComponentView should not raise UI Automation focus events at all. It is a host only; accessibility focus should be raised by the XAML content inside the island.
Activity
iamAbhi-916 commentedon Jan 22, 2026
This works caps and arrow keys; this is a bug for tab key itslef . This would be taken up for minor release of 0.82!
HariniMalothu17 commentedon Jan 27, 2026
Adding on to what the issue is:
observed an accessibility issue when navigating XAML controls hosted inside a ContentIsland in React Native Windows with Narrator enabled. Keyboard focus works correctly: Tab navigation moves focus to the XAML control, and keyboard interaction behaves as expected. The problem is not focus navigation.
The issue is with UI Automation focus. When focus moves into a XAML island, RNW raises the UI Automation focus event on the ContentIsland (container) instead of the XAML control. Since Narrator follows UI Automation focus (not keyboard focus directly), it announces the container (“Pane”) rather than the actual control.
Verified that XAML already provides correct accessibility and that overriding or creating automation peers is not required.
This confirms the problem is framework-level, specifically in the UI Automation focus event path.
The intended design is that ContentIslandComponentView should not raise UI Automation focus events at all. It is a host only; accessibility focus should be raised by the XAML content inside the island.