It's unclear whether this needs an intent to prototype/ship given that it isn't a feature exposed to web content. However, after some discussion, it certainly can't hurt to provide notice even if it's not required.
As of Firefox 143, I intend to turn Windows UI Automation on by default.
Summary:
UI Automation (UIA) is Microsoft's recommended accessibility framework for Windows, replacing the earlier Microsoft Active Accessibility (MSAA) framework. Although it is not yet used for the web by popular screen readers such as NVDA and JAWS, it is used by an increasing number of applications, including accessibility tools built into Windows such as Narrator, Text Cursor Indicator, Windows Speech Recognition and Voice Access. Furthermore, it is used by Windows features not specifically targeted at accessibility such as Suggested Actions and Snap Layouts. It offers several advantages over older frameworks including increased performance and security.
Specification: UIA is not a web or open standard, though mappings for web content are standardised by the W3C ARIA Working Group:
Platform coverage: Windows only, exposed to external accessibility clients (not a web API)
Preference: accessibility.uia.enable (0 to disable, 1 to force enable, 2 to enable unless an incompatible client is detected)
DevTools bug: not applicable; not relevant to web developers. Any inspection, debugging, etc. specific to UIA is performed using Windows specific tools.
Other browsers:
Edge: shipped (version unknown)
WebKit: not applicable; UIA is Windows only
Security & Privacy Concerns: Exposes the same information already available to accessibility clients using other accessibility APIs across all supported platforms. Doesn't expose anything to web content.
Jamie