Merge pull request #7771 from Mikejo5000/mikejo-acc

Updates for accessibility

Author: PRMerger8

docs/debugger/attach-to-running-processes-with-the-visual-studio-debugger.md

@@ -32,7 +32,7 @@ ms.workload:
 ---
 # Attach to running processes with the Visual Studio debugger
 
-You can attach the Visual Studio debugger to a running process on a local or remote computer. After the process is running, select **Debug** > **Attach to Process** or press **Ctrl**+**Alt**+**P** in Visual Studio, and use the **Attach to Process** dialog to attach the debugger to the process.
+You can attach the Visual Studio debugger to a running process on a local or remote computer. After the process is running, select **Debug** > **Attach to Process** or press **Ctrl**+**Alt**+**p** in Visual Studio, and use the **Attach to Process** dialog to attach the debugger to the process.
 
 You can use **Attach to Process** to debug running apps on local or remote computers, debug multiple processes simultaneously, debug apps that weren't created in Visual Studio, or debug any app you didn't start from Visual Studio with the debugger attached. For example, if you're running an app without the debugger and hit an exception, you can then attach the debugger to the process running the app and begin debugging.
 

docs/debugger/debugger-feature-tour.md

@@ -87,7 +87,7 @@ This command resumes app execution (and advances the debugger) until the current
 
 ## Run to cursor
 
-When you are editing code (rather than paused in the debugger), right-click a line of code in your app and choose **Run to Cursor**. This command starts debugging and sets a temporary breakpoint on the current line of code.
+When you are editing code (rather than paused in the debugger), right-click a line of code in your app and choose **Run to Cursor** (or press **Ctrl** to **F10**). This command starts debugging and sets a temporary breakpoint on the current line of code.
 
 ![Run to Cursor](../debugger/media/dbg-tour-run-to-cursor.png "Run to Cursor")
 
@@ -102,7 +102,7 @@ This command is useful when you are editing code and want to quickly set a tempo
 
 ## Restart your app quickly
 
-Click the **Restart** ![Restart App](../debugger/media/dbg-tour-restart.png "Restart App") button in the Debug Toolbar (**Ctrl + Shift +F5**).
+Click the **Restart** ![Restart App](../debugger/media/dbg-tour-restart.png "Restart App") button in the Debug Toolbar (or press **Ctrl + Shift + F5**).
 
 When you press **Restart**, it saves time versus stopping the app and restarting the debugger. The debugger pauses at the first breakpoint that is hit by executing code.
 

docs/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md

@@ -212,7 +212,7 @@ During debugging, the **Modules** window shows the code modules the debugger is
 
 **To monitor or change symbol locations or options while debugging:**
 
-1. To open the **Modules** window, while debugging, select **Debug** > **Windows** > **Modules**.
+1. To open the **Modules** window, while debugging, select **Debug** > **Windows** > **Modules** (or press **Ctrl** + **Alt** + **U**).
 1. In the **Modules** window, right-click the **Symbol Status** or **Symbol File** headers, or any module.
 1. In the context menu, select one of the following options:
 

docs/debugger/using-breakpoints.md

@@ -79,7 +79,7 @@ You can control when and where a breakpoint executes by setting conditions. The
 
 **To set a breakpoint condition:**
 
-1. Right-click the breakpoint symbol and select **Conditions**. Or hover over the breakpoint symbol, select the **Settings** icon, and then select **Conditions** in the **Breakpoint Settings** window.
+1. Right-click the breakpoint symbol and select **Conditions** (or press **Alt** + **F9**, **C**). Or hover over the breakpoint symbol, select the **Settings** icon, and then select **Conditions** in the **Breakpoint Settings** window.
 
    You can also set conditions in the **Breakpoints** window by right-clicking a breakpoint and selecting **Settings**, and then selecting **Conditions**.
 
@@ -118,7 +118,7 @@ If you set a breakpoint condition with invalid syntax, a warning message appears
 
 1. Set a breakpoint in the code some place after the object has been created.
 
-2. Start debugging, and when execution pauses at the breakpoint, select **Debug** > **Windows** > **Locals** or **Alt**+**4** to open the **Locals** window.
+2. Start debugging, and when execution pauses at the breakpoint, select **Debug** > **Windows** > **Locals** (or press **Ctrl** + **Alt** + **V**, **L**) to open the **Locals** window.
 
    Find the specific object instance in the **Locals** window, right-click it, and select **Make Object ID**.
 
@@ -163,7 +163,7 @@ You can break execution when a function is called. This is useful, for example,
 
 **To set a function breakpoint:**
 
-1. Select **Debug** > **New Breakpoint** > **Function Breakpoint**, or press **Alt**+**F9** > **Ctrl**+**B**.
+1. Select **Debug** > **New Breakpoint** > **Function Breakpoint**, or press **Ctrl** + **K**, **B**.
 
    You can also select **New** > **Function Breakpoint** in the **Breakpoints** window.
 
@@ -200,7 +200,7 @@ You can break execution when a function is called. This is useful, for example,
 
 2. Find the address of the instance (for example, `0xcccccccc`).
 
-3. Select **Debug** > **New Breakpoint** > **Function Breakpoint**, or press **Alt**+**F9** > **Ctrl**+**B**.
+3. Select **Debug** > **New Breakpoint** > **Function Breakpoint**, or press **Ctrl** + **K**, **B**.
 
 4. Add the following to the **Function Name** box, and select **C++** language.
 
@@ -237,7 +237,7 @@ Data breakpoints in .NET Core won't work for:
 
 **To set a data breakpoint:**
 
-1. In a C++ project, start debugging, and wait until a breakpoint is reached. On the **Debug** menu, choose **New Breakpoint** > **Data Breakpoint**
+1. In a C++ project, start debugging, and wait until a breakpoint is reached. On the **Debug** menu, choose **New Breakpoint** > **Data Breakpoint**.
 
     You can also select **New** > **Data Breakpoint** in the **Breakpoints** window or right-click an item in the **Autos**, **Watch**, or **Locals** window and select **Break when value changes** in the context menu.
 
@@ -262,7 +262,7 @@ Data breakpoints don't work under the following conditions:
 
 In the **Breakpoints** window, you can search, sort, filter, enable/disable, or delete breakpoints. You can also set conditions and actions, or add a new function or data breakpoint.
 
-To open the **Breakpoints** window, select **Debug** > **Windows** > **Breakpoints**, or press **Alt**+**F9** or **Ctrl**+**Alt**+**B**.
+To open the **Breakpoints** window, select **Debug** > **Windows** > **Breakpoints**, or press **Ctrl**+**Alt**+**B**.
 
 ![Breakpoints window](../debugger/media/breakpointswindow.png "Breakpoints window")
 
@@ -308,7 +308,7 @@ To visually trace breakpoints during code execution, see [Map methods on the cal
 
 ### Set a breakpoint in the Disassembly window
 
-1. To open the **Disassembly** window, you must be paused during debugging. Select **Debug** > **Windows** > **Disassembly**, or press **Alt**+**8**.
+1. To open the **Disassembly** window, you must be paused during debugging. Select **Debug** > **Windows** > **Disassembly**, or press **Ctrl**+**Alt**+**D**.
 
 2. In the **Disassembly** window, click in the left margin of the instruction you want to break at. You can also select it and press **F9**, or right-click and select **Breakpoint** > **Insert Breakpoint**.
 

docs/test/getting-started-with-unit-testing.md

@@ -174,13 +174,13 @@ This section describes how to create a unit test project.
 1. Open [Test Explorer](../test/run-unit-tests-with-test-explorer.md).
 
    ::: moniker range=">=vs-2019"
-   To open Test Explorer, choose **Test** > **Test Explorer** from the top menu bar.
+   To open Test Explorer, choose **Test** > **Test Explorer** from the top menu bar (or press **Ctrl** + **E**, **T**).
    ::: moniker-end
    ::: moniker range="vs-2017"
    To open Test Explorer, choose **Test** > **Windows** > **Test Explorer** from the top menu bar.
    ::: moniker-end
 
-1. Run your unit tests by clicking **Run All**.
+1. Run your unit tests by clicking **Run All** (or press **Ctrl** + **R**, **V**).
 
    ![Run unit tests in Test Explorer](media/vs-2019/test-explorer-run-all.png)
 
@@ -268,7 +268,7 @@ To add a unit test project:
 
    ![Add code to your unit test code file](media/vs-2019/unit-test-method.png)
 
-6. Run the test from **Test Explorer** or by right-clicking on the test code and choosing **Run Test(s)**.
+6. Run the test from **Test Explorer** or by right-clicking on the test code and choosing **Run Test(s)** (or **Ctrl** + **R**, **T**).
 
 ## Next steps
 

docs/test/run-unit-tests-with-test-explorer.md

@@ -28,7 +28,7 @@ Visual Studio includes the Microsoft unit testing frameworks for both managed an
 
 ## Run tests in Test Explorer
 
-When you build the test project, the tests appear in Test Explorer. If Test Explorer is not visible, choose **Test** on the Visual Studio menu, choose **Windows**, and then choose **Test Explorer**.
+When you build the test project, the tests appear in Test Explorer. If Test Explorer is not visible, choose **Test** on the Visual Studio menu, choose **Windows**, and then choose **Test Explorer** (or press **Ctrl** + **E**, **T**).
 
 ::: moniker range="vs-2017"
 ![Unit Test Explorer](../test/media/ute_failedpassednotrunsummary.png)
@@ -58,11 +58,11 @@ You can perform much of the work of finding, organizing and running tests from t
 ::: moniker range="vs-2017"
 You can run all the tests in the solution, all the tests in a group, or a set of tests that you select. Do one of the following:
 
-- To run all the tests in a solution, choose **Run All**.
+- To run all the tests in a solution, choose **Run All** (or press **Ctrl** + **R**, **V**).
 
 - To run all the tests in a default group, choose **Run** and then choose the group on the menu.
 
-- Select the individual tests that you want to run, open the right-click menu for a selected test and then choose **Run Selected Tests**.
+- Select the individual tests that you want to run, open the right-click menu for a selected test and then choose **Run Selected Tests** (or press **Ctrl** + **R**, **T**).
 
 - If individual tests have no dependencies that prevent them from being run in any order, turn on parallel test execution with the ![Screenshot of the Parallel test execution toggle button on the Visual Studio Test Explorer toolbar. When this button is selected, tests will run in parallel.](../test/media/ute_parallelicon-small.png) toggle button on the toolbar. This can noticeably reduce the time taken to run all the tests.
 
@@ -71,11 +71,11 @@ The **pass/fail bar** at the top of the **Test Explorer** window is animated as
 ::: moniker range=">=vs-2019"
 You can run all the tests in the solution, all the tests in a group, or a set of tests that you select. Do one of the following:
 
-- To run all the tests in a solution, choose the **Run All** icon.
+- To run all the tests in a solution, choose the **Run All** icon (or press **Ctrl** + **R**, **V**).
 
 - To run all the tests in a default group, choose the **Run** icon and then choose the group on the menu.
 
-- Select the individual tests that you want to run, open the right-click menu for a selected test and then choose **Run Selected Tests**.
+- Select the individual tests that you want to run, open the right-click menu for a selected test and then choose **Run Selected Tests** (or press **Ctrl** + **R**, **T**).
 
 - If individual tests have no dependencies that prevent them from being run in any order, turn on parallel test execution in the settings menu of the toolbar. This can noticeably reduce the time taken to run all the tests.
 ::: moniker-end
@@ -124,7 +124,7 @@ If the test fails, the details pane also displays:
 
 ### View the source code of a test method
 
-To display the source code for a test method in the Visual Studio editor, select the test and then choose **Open Test** on the right-click menu (Keyboard: **F12**).
+To display the source code for a test method in the Visual Studio editor, select the test and then choose **Open Test** on the right-click menu (or press **F12**).
 
 ## Group and filter the test list
 

docs/test/unit-test-basics.md

@@ -230,7 +230,7 @@ public void My_Test ()
 
 ## Run tests in Test Explorer
 
-When you build the test project, the tests appear in **Test Explorer**. If **Test Explorer** is not visible, choose **Test** on the Visual Studio menu, choose **Windows**, and then choose **Test Explorer**.
+When you build the test project, the tests appear in **Test Explorer**. If **Test Explorer** is not visible, choose **Test** on the Visual Studio menu, choose **Windows**, and then choose **Test Explorer** (or press **Ctrl** + **E**, **T**).
 
 ::: moniker range="vs-2017"
 ![Unit Test Explorer](../test/media/ute_failedpassednotrunsummary.png)
@@ -254,7 +254,7 @@ The **Test Explorer** toolbar helps you discover, organize, and run the tests th
 ![Run tests from the Test Explorer toolbar](../test/media/vs-2019/test-explorer-toolbar-diagram-16-2.png)
 ::: moniker-end
 
-You can choose **Run All** to run all your tests, or choose **Run** to choose a subset of tests to run. Select a test to view the details of that test in the test details pane. Choose **Open Test** from the right-click menu (Keyboard: **F12**) to display the source code for the selected test.
+You can choose **Run All** to run all your tests (or press **Ctrl** + **R**, **V**), or choose **Run** to choose a subset of tests to run (**Ctrl** + **R**, **T**). Select a test to view the details of that test in the test details pane. Choose **Open Test** from the right-click menu (Keyboard: **F12**) to display the source code for the selected test.
 
 ::: moniker range="vs-2017"
 

docs/test/walkthrough-creating-and-running-unit-tests-for-managed-code.md

@@ -132,7 +132,7 @@ This article steps you through creating, running, and customizing a series of un
 
 6. Rename the file to *BankAccount.cs* by right-clicking and choosing **Rename** in **Solution Explorer**.
 
-7. On the **Build** menu, click **Build Solution**.
+7. On the **Build** menu, click **Build Solution** (or press **Ctrl** + **SHIFT** + **B**).
 
 You now have a project with methods you can test. In this article, the tests focus on the `Debit` method. The `Debit` method is called when money is withdrawn from an account.
 
@@ -181,7 +181,7 @@ Create a test class to verify the `BankAccount` class. You can use the *UnitTest
 
 ### Rename a file and class
 
-1. To rename the file, in **Solution Explorer**, select the *UnitTest1.cs* file in the BankTests project. From the right-click menu, choose **Rename**, and then rename the file to *BankAccountTests.cs*.
+1. To rename the file, in **Solution Explorer**, select the *UnitTest1.cs* file in the BankTests project. From the right-click menu, choose **Rename** (or press **F2**), and then rename the file to *BankAccountTests.cs*.
 
 ::: moniker range="vs-2017"
 
@@ -191,7 +191,7 @@ Create a test class to verify the `BankAccount` class. You can use the *UnitTest
 
 ::: moniker range=">=vs-2019"
 
-2. To rename the class, position the cursor on `UnitTest1` in the code editor, right-click, and then choose **Rename**. Type in **BankAccountTests** and then press **Enter**.
+2. To rename the class, position the cursor on `UnitTest1` in the code editor, right-click, and then choose **Rename** (or press **F2**). Type in **BankAccountTests** and then press **Enter**.
 
 ::: moniker-end
 
@@ -283,11 +283,11 @@ A test method must meet the following requirements:
 
 ## Build and run the test
 
-1. On the **Build** menu, choose **Build Solution**.
+1. On the **Build** menu, choose **Build Solution** (or press **Ctrl** + **SHIFT** + **B**).
 
-2. If **Test Explorer** is not open, open it by choosing **Test** > **Windows** > **Test Explorer** from the top menu bar.
+2. If **Test Explorer** is not open, open it by choosing **Test** > **Windows** > **Test Explorer** from the top menu bar (or press **Ctrl** + **E**, **T**).
 
-3. Choose **Run All** to run the test.
+3. Choose **Run All** to run the test (or press **Ctrl** + **R**, **V**).
 
    While the test is running, the status bar at the top of the **Test Explorer** window is animated. At the end of the test run, the bar turns green if all the test methods pass, or red if any of the tests fail.
 
@@ -317,7 +317,7 @@ m_balance -= amount;
 
 ### Rerun the test
 
-In **Test Explorer**, choose **Run All** to rerun the test. The red/green bar turns green to indicate that the test passed.
+In **Test Explorer**, choose **Run All** to rerun the test (or press **Ctrl** + **R**, **V**). The red/green bar turns green to indicate that the test passed.
 
 ![Test Explorer in Visual Studio 2019 showing passed test](media/test-explorer-banktests-passed.png)