UI Automation in Windows Console: revert for 2019.3

[codeofdusk]

Link to issue number:

Completes #10682.

Summary of the issue:

It was decided to revert to legacy console support for 2019.3, but various UI and user guide elements remain from #9771.

Description of how this pull request fixes the issue:

• The auto config setting is reverted to 2019.2 behavior (i.e. it maps to legacy).
• The UI is returned to 2019.2 state (i.e. a simple checkbox). We really should move users to UIA once it becomes the default, and users who turn on UIA to experiment during development and then switch back to legacy wouldn’t automatically be upgraded.
• References to “legacy” consoles removed from UI and user guide.

Testing performed:

Tested an upgrade from NVDA 2019.2.1 (stable) to this PR. Insured that legacy console is used by default and the UIA checkboxes are functional.

Known issues with pull request:

None.

Change log entry:

None needed.

[AppVeyorBot]

• Build (for testing PR)
• Unit test failure

See test results for failed build of commit 54af3039b9

[AppVeyorBot]

• Unit test failure
• Build (for testing PR)

See test results for failed build of commit 664f1014ad

[AppVeyorBot]

• PR introduces Flake8 errors
• Build (for testing PR)

See test results for failed build of commit 31d53948c5

[AppVeyorBot]

• PR introduces Flake8 errors
• Build (for testing PR)

See test results for failed build of commit cfbf2d636c

[AppVeyorBot]

• PR introduces Flake8 errors
• Build (for testing PR)

See test results for failed build of commit eed2b734c3

[codeofdusk]

Cc @LeonarddeR @michaelDCurran

[AppVeyorBot]

• PR introduces Flake8 errors
• Build (for testing PR)

See test results for failed build of commit 2eaecfc37c

[michaelDCurran]

the 'and's need to be on the start of the next line to stop the linting issues I think.

[AppVeyorBot]

• Build (for testing PR)

See test results for failed build of commit 0cbdf3b736

[AppVeyorBot]

• Build (for testing PR)

See test results for failed build of commit 5252086610

[LeonarddeR]

I think this was already done using the https://github.com/nvaccess/nvda/tree/legacyWinConsoleByDefault branch

[AppVeyorBot]

• Build (for testing PR)

See test results for failed build of commit 8a4e6562ec

[codeofdusk]

I think this was already done using the https://github.com/nvaccess/nvda/tree/legacyWinConsoleByDefault branch

No, not quite. This PR reverts some additional UI, user guide, and behavior changes that were needed when UIA was the default.

[codeofdusk]

I think this was already done using the https://github.com/nvaccess/nvda/tree/legacyWinConsoleByDefault branch

No, not quite. This PR reverts some additional UI, user guide, and behavior changes that were needed when UIA was the default.

It also keeps "auto" as the default config spec setting, allowing users to freely enable/disable UIA console during development and be automatically switched when it becomes the default.

[AppVeyorBot]

• PR introduces Flake8 errors
• Build (for testing PR)

See test results for failed build of commit 5942d1788e