created and maintained by @carlos-zamora

A number of screen readers still don't use the UIA framework we've exposed in ConHost and Windows Terminal. After speaking with @codeofdusk, there's a number of suggested improvements we can do to convince screen reader manufacturers to switch over from the legacy framework.

• Create separate UIA parent objects for standard and alt conhost buffers #5406: Standard and alt buffer distinction
• Feature Idea: Find/Extract Text Attributes for Accessibility #2161: Expose text attributes
• Properly handle and test "end of buffer" in UiaTextRange #6986: Better "end of buffer" handling (trim whitespace)
• UIA: incorrect word boundary #7960: Word navigation bug

With this changes, we can...

• build a case for NVDA to use UIA by default (see UI Automation in Windows Console: make default in FORMATTED consoles (Windows 11 Sun Valley 2) nvaccess/nvda#10964)
• help NVDA remove reduce their use of all of their workarounds from pre-Refactor UiaTextRange For Improved Navigation and Reliability #4018
• improve performance, stability, and accessibility for ConHost and Windows Terminal when using screen readers (i.e. password detection)

see also:

• Fix UIA Word movement tests #11253