Virtualized node exposure vs full tree announcement in Solution Explorer for large solutions

Goal is reliable screen reader navigation of Solution Explorer in large solutions without degrading IDE responsiveness.

Visual Studio virtualizes Solution Explorer items for performance. Virtualization limits the UI Automation tree depth exposed to assistive technology, which constrains discoverability for screen reader users. Full tree exposure would improve discoverability and announcement completeness but risks UI lag and longer announcement sequences under hundreds of projects.

The design decision around information exposure versus performance for accessibility is unresolved in user-facing workflows. Version assumptions apply to Visual Studio 2022 desktop edition.

What is the documented UI Automation exposure policy for virtualized Solution Explorer nodes in Visual Studio 2022 desktop?

How does the IDE determine which nodes are announced to screen readers when the tree is virtualized?

Is there a documented accessibility mode or setting that changes virtualization behavior for screen reader users?