Visual Studio 2022 (17.11)
Accessibility Conformance Report published by Microsoft
Conformance by level
Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.
Level A — 30 criteria
- Supports
- 15
- Partially supports
- 6
- Does not support
- 0
- Not applicable
- 9
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 11
- Partially supports
- 3
- Does not support
- 1
- Not applicable
- 5
- Not evaluated
- 0
Level AAA — 28 criteria
- Supports
- 0
- Partially supports
- 0
- Does not support
- 0
- Not applicable
- 0
- Not evaluated
- 28
Source: Download the original report from Microsoft (Word document). Or browse all of Microsoft's reports on Microsoft's own site.
These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.
All reported criteria (78)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Supports | |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | |
| 1.3.1 | Info and Relationships | A | Partially Supports | In Cloud Service projects in the Diagnostics Configuration dialog, some screen readers may not announce when a radio button is selected or deselected.There are a few different accessibility issues in “Tools” -> "Options" -> “Debugging” -> “Output Window” page. For example, when the focus is at the name of the option, Narrator announces the control type as “Button”, which is not really a button. When the focus is at the value and the user changes the value, Narrator doesn’t announce the new value. The keyboard navigation isn’t intuitive. The user has to focus on the name of the option before moving to the next option. Additionally, section groups are not always read correctly.Screen reader doesn't read the second column in Autos, Locals, and Watch window.In the Parallel Stacks window, the Method View visualization of the window does not allow proper navigation via keyboard and screen readers will give false relationship data.While using Quick Actions in the XAML Designer, Narrator may not announce some of the text information present in the popup.Narrator may not announce the selected dropdown option name after selecting an option from the "Execution mode" dropdown in "Properties > iOS Run options" for iOS projects.Screen readers may announce all information on the "Properties > Debug" page for WinForms apps instead of the relevant section when closing the Authentication mode combo box using the escape key.Screen readers may announce the incorrect sorting state for column headers in the error list window.In the bookmarks tool window, when using a screen reader, it is difficult to establish the relationship between a given element in the name column and its corresponding value in the line number or file location columns.When navigating the Android Device Manager with a screen reader, it is not possible to use Ctrl+Alt+Arrow Keys to read data in the table cells.Narrator may not announce the selected dropdown option name after selecting an option from the "Provider" dropdown when adding a new client-side library to an app.When comparing schemas using SQL Server Object Explorer, screen readers may not announce the selected state for items in the Object Types tab of the Schema Compare Options window.Screen readers may not announce all information in the problem details dialog.Screen readers may not announce all information present in the error list.For certain C++ and CMake projects, narrator may not announce items in the command line arguments and attach to process combo boxes when using keyboard arrow keys.Screen readers may announce the state for debug target options as unchecked even if it's selected when navigating its list using the keyboard arrow keys. |
| 1.3.2 | Meaningful Sequence | A | Supports | |
| 1.3.3 | Sensory Characteristics | A | Supports | |
| 1.4.1 | Use of Color | A | Supports | |
| 1.4.2 | Audio Control | A | Not Applicable | |
| 2.1.1 | Keyboard | A | Partially Supports | In some cases, in Visual Studio, users cannot use keyboard to show the tooltip of a control. Many of these issues can be solved by upgrading to the latest versions of Windows 11. While inspecting a performance report from the profiler, users are not able to use the keyboard to navigate to all of the elements in the report. Screen reader users will have difficulty determining all the contents of the report.Users who rely on the Data Source selector for Web Forms may encounter issues with selecting an OLE DB providerTable controls throughout Visual Studio may not provide keyboard-accessible methods for adjusting the width of individual columns or accessing column headers in general.The Problem details dialog for C++ projects is not accessible via keyboard.Tooltips associated with combo boxes without fixed values cannot be accessed using the keyboard. |
| 2.1.2 | No Keyboard Trap | A | Partially Supports | While inspecting the Performance Tools options in the Tools > Options dialog, users cannot use the Tab or Arrow keys exclusively to navigate the elements of the window and focus order is not consistent between Tab and Arrow keys. Screen reader users may not be able to determine the flow of the window. |
| 2.1.4 | Character Key Shortcuts | A | Supports | |
| 2.2.1 | Timing Adjustable | A | Not Applicable | |
| 2.2.2 | Pause, Stop, Hide | A | Not Applicable | |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | |
| 2.4.1 | Bypass Blocks | A | Not Applicable | |
| 2.4.2 | Page Titled | A | Not Applicable | |
| 2.4.3 | Focus Order | A | Partially Supports | Users navigating the WinForms Designer Options may not be notified when the drop down for "Auto Load Controls in the ToolBox" has focus. Be advised that the user may use the keyboard up/down arrows to cycle through the available options when the text in the corresponding text box is selected.In the Containers tool window, focus order may not be logical for some controls.In the Build Insights tool window for C++ projects, backing out of an expanded filter for the Project Column table header does not shift focus back to the filter control. |
| 2.4.4 | Link Purpose (In Context) | A | Supports | |
| 2.5.1 | Pointer Gestures | A | Supports | |
| 2.5.2 | Pointer Cancellation | A | Supports | |
| 2.5.3 | Label in Name | A | Supports | |
| 2.5.4 | Motion Actuation | A | Not Applicable | |
| 3.1.1 | Language of Page | A | Supports | |
| 3.2.1 | On Focus | A | Partially Supports | In some cases, when interacting with the File type dropdown in the Properties tool window with the keyboard, the entries will automatically be selected without the user selecting the enter key. |
| 3.2.2 | On Input | A | Supports | |
| 3.3.1 | Error Identification | A | Supports | |
| 3.3.2 | Labels or Instructions | A | Supports | |
| 4.1.1 | Parsing | A | Supports | |
| 4.1.2 | Name, Role, Value | A | Partially Supports | Some tree controls in Visual Studio do not correctly announce when node elements are expanded or collapsed with the keyboard, even if the operation is completing successfully.Some elements of the .NET MAUI / Xamarin Property Panel have children with non-unique names and may be difficult to differentiate for some users.Users who rely on Assistive Technologies may have difficulties using the ASP.NET ListViewControl, Data Source Configuration Wizard, Table Adapter Configuration Wizard, Access Permission list items on the Data Link Properties dialog, Query Builder dialog, Workflow Designer Property Panel, and the Table Adapter Configuration Wizard.In debugging, the user can inspect the Thread window. But user using screen reader won’t know that the row is about a process group instead of a thread. Besides, there is a button to expand/collapse the threads that belong to the process. Screen reader doesn’t announce what the button is for. The button doesn’t have the property IsExpandCollapsePatternAvailable. Users using assistive technology won’t know that they can expand or collapse the threads.The WinForms Property Browser ToolStrip contains buttons to change the layout of the Property Browser from categorized to alphabetized and from control properties to control events. Some users may not be able to determine the state of these toggle buttons and will need to enter the Property Browser to determine its layout.Disabled text may be difficult to read when setting up data binding properties of WinForms controls in the Formatting and Advanced Binding Dialog of the WinForms Designer when the user is in High Contrast Mode. Multiple controls in this page are not using the disabled text color provided by the Operating System.Visual Studio Installer experience has known issues when used with Narrator.Some screen readers do not announce the names of the buttons in the toolbar associated with the Android Emulator.Some descriptive name properties are not defined for UI elements in the Properties > Code Analysis > Clang-Tidy page for a C++ project. |
| 1.2.4 | Captions (Live) | AA | Not Applicable | |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | |
| 1.3.4 | Orientation | AA | Supports | |
| 1.3.5 | Identify Input Purpose | AA | Supports | |
| 1.4.3 | Contrast (Minimum) | AA | Supports | |
| 1.4.4 | Resize text | AA | Supports | |
| 1.4.5 | Images of Text | AA | Supports | |
| 1.4.10 | Reflow | AA | Partially Supports | Users who attempt to interact with Visual Studio at an effective resolution below the Visual Studio stated minimum requirements (1280x720) may experience truncated UI or other visual issues. |
| 1.4.11 | Non-text Contrast | AA | Supports | |
| 1.4.12 | Text Spacing | AA | Supports | |
| 1.4.13 | Content on Hover or Focus | AA | Does Not Support | Tooltips in Visual Studio do not currently support content on Hover or Focus. |
| 2.4.5 | Multiple Ways | AA | Not Applicable | |
| 2.4.6 | Headings and Labels | AA | Supports | |
| 2.4.7 | Focus Visible | AA | Partially Supports | Keyboard focus is not visible in the "Look in" list items pane While inspecting a performance report from the profiler, the focus indicator can be lost when placed on elements in the report. Users who rely on the keyboard to operate the report will have difficulty determining the component on which keyboard operations will interact. |
| 3.1.2 | Language of Parts | AA | Not Applicable | |
| 3.2.3 | Consistent Navigation | AA | Not Applicable | |
| 3.2.4 | Consistent Identification | AA | Supports | |
| 3.3.3 | Error Suggestion | AA | Supports | |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | |
| 4.1.3 | Status Messages | AA | Partially Supports | Some screen readers may not announce status messages that appear in the add new scaffolding item dialog.Some screen readers may not announce status messages that populate in the terminal. |
| 1.2.6 | Sign Language (Prerecorded) | AAA | Not Evaluated | |
| 1.2.7 | Extended Audio Description (Prerecorded) | AAA | Not Evaluated | |
| 1.2.8 | Media Alternative (Prerecorded) | AAA | Not Evaluated | |
| 1.2.9 | Audio-only (Live) | AAA | Not Evaluated | |
| 1.3.6 | Identify Purpose | AAA | Not Evaluated | |
| 1.4.6 | Contrast (Enhanced) | AAA | Not Evaluated | |
| 1.4.7 | Low or No Background Audio | AAA | Not Evaluated | |
| 1.4.8 | Visual Presentation | AAA | Not Evaluated | |
| 1.4.9 | Images of Text (No Exception) | AAA | Not Evaluated | |
| 2.1.3 | Keyboard (No Exception) | AAA | Not Evaluated | |
| 2.2.3 | No Timing | AAA | Not Evaluated | |
| 2.2.4 | Interruptions | AAA | Not Evaluated | |
| 2.2.5 | Re-authenticating | AAA | Not Evaluated | |
| 2.2.6 | Timeouts | AAA | Not Evaluated | |
| 2.3.2 | Three Flashes | AAA | Not Evaluated | |
| 2.3.3 | Animation from Interactions | AAA | Not Evaluated | |
| 2.4.8 | Location | AAA | Not Evaluated | |
| 2.4.9 | Link Purpose (Link Only) | AAA | Not Evaluated | |
| 2.4.10 | Section Headings | AAA | Not Evaluated | |
| 2.5.5 | Target Size | AAA | Not Evaluated | |
| 2.5.6 | Concurrent Input Mechanisms | AAA | Not Evaluated | |
| 3.1.3 | Unusual Words | AAA | Not Evaluated | |
| 3.1.4 | Abbreviations | AAA | Not Evaluated | |
| 3.1.5 | Reading Level | AAA | Not Evaluated | |
| 3.1.6 | Pronunciation | AAA | Not Evaluated | |
| 3.2.5 | Change on Request | AAA | Not Evaluated | |
| 3.3.5 | Help | AAA | Not Evaluated | |
| 3.3.6 | Error Prevention (All) | AAA | Not Evaluated |
Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.
Get told when this changes
This report is dated October 24, 2024. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.