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
Copy file name to clipboardExpand all lines: user_docs/en/userGuide.t2t
+10-2Lines changed: 10 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1888,8 +1888,16 @@ This setting contains the following values:
1888
1888
- Always: where ever UI automation is available in Microsoft word (no matter how complete).
1889
1889
-
1890
1890
1891
-
==== Use UI Automation to access the Windows Console when available ====[AdvancedSettingsConsoleUIA]
1892
-
When this option is enabled, NVDA will use a new, work in progress version of its support for Windows Console which takes advantage of [accessibility improvements made by Microsoft https://devblogs.microsoft.com/commandline/whats-new-in-windows-console-in-windows-10-fall-creators-update/]. This feature is highly experimental and is still incomplete, so its use is not yet recommended. However, once completed, it is anticipated that this new support will become the default, improving NVDA's performance and stability in Windows command consoles.
1891
+
==== Windows Console support ====[AdvancedSettingsConsoleUIA]
1892
+
This option selects how NVDA interacts with the Windows Console used by command prompt, PowerShell, and the Windows Subsystem for Linux.
1893
+
It does not affect the modern Windows Terminal.
1894
+
In Windows 10 version 1709, Microsoft [added support for its UI Automation API to the console https://devblogs.microsoft.com/commandline/whats-new-in-windows-console-in-windows-10-fall-creators-update/], bringing vastly improved performance and stability for screen readers that support it.
1895
+
In situations where UI Automation is unavailable or known to result in an inferior user experience, NVDA's legacy console support is available as a fallback.
1896
+
The Windows Console support combo box has three options:
1897
+
- Automatic: This option is currently equivalent to "legacy". However, with this option selected, NVDA will begin using UI Automation in consoles automatically in a future version once it has become stable and suitable for wider use.
1898
+
- UIA when available: Uses UI Automation in consoles if available, even for versions with incomplete or buggy implementations. Though not yet fully stable, UI Automation may provide a superior user experience in some scenarios, especially in the Windows 11 Sun Valley 2 (22H2) update.
1899
+
- Legacy: UI Automation in the Windows Console will be completely disabled, so the legacy fallback will always be used even in situations where UI Automation would provide a superior user experience. Therefore, selecting this option is not recommended unless you know what you are doing.
1900
+
-
1893
1901
1894
1902
==== Use UIA with Microsoft Edge and other Chromium based browsers when available ====[ChromiumUIA]
1895
1903
Allows specifying when UIA will be used when it is available in Chromium based browsers such as Microsoft Edge.
0 commit comments