What would you like to be added?
Add first-class accessibility and automation bridges for the Skia Android and iOS renderers. The WinUI AutomationPeer tree should be translated into native Android accessibility nodes and iOS accessibility elements so TalkBack, VoiceOver, UIAutomator, XCUITest, and Appium-compatible tooling can discover and operate Uno controls.
The implementation should cover semantic identity, roles, names, values, states, relationships, actions, focus synchronization, live updates, rich-control patterns, virtualization, lifecycle cleanup, and secure-text redaction.
Why is this needed?
Skia applications on mobile currently lack native accessibility integration comparable to Uno's Win32, WebAssembly, and macOS backends. This prevents screen-reader users from reliably navigating and operating controls and prevents mobile automation tools from locating controls through stable accessibility identifiers.
Renderer
For which platforms
Anything else we need to know?
The public design and acceptance criteria are tracked in specs/005-mobile-a11y-automation/. Native Android execution is covered by the implementation evidence; native iOS and VoiceOver/XCUITest validation require the macOS CI runner.
What would you like to be added?
Add first-class accessibility and automation bridges for the Skia Android and iOS renderers. The WinUI
AutomationPeertree should be translated into native Android accessibility nodes and iOS accessibility elements so TalkBack, VoiceOver, UIAutomator, XCUITest, and Appium-compatible tooling can discover and operate Uno controls.The implementation should cover semantic identity, roles, names, values, states, relationships, actions, focus synchronization, live updates, rich-control patterns, virtualization, lifecycle cleanup, and secure-text redaction.
Why is this needed?
Skia applications on mobile currently lack native accessibility integration comparable to Uno's Win32, WebAssembly, and macOS backends. This prevents screen-reader users from reliably navigating and operating controls and prevents mobile automation tools from locating controls through stable accessibility identifiers.
Renderer
For which platforms
Anything else we need to know?
The public design and acceptance criteria are tracked in
specs/005-mobile-a11y-automation/. Native Android execution is covered by the implementation evidence; native iOS and VoiceOver/XCUITest validation require the macOS CI runner.