ACR Index Get a draft ACR

Visual Studio 2019

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.

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 (50)

Conformance as stated by Microsoft in its published report.
CriterionNameLevel ConformanceRemarks from vendor
1.1.1 Non-text Content A Partially Supports Some non-text buttons in the Xamarin iOS designer do not have tooltips that are accessible to keyboard-only users.
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.2.4 Captions (Live) AA Not Applicable
1.2.5 Audio Description (Prerecorded) AA Not Applicable
1.3.1 Info and Relationships A Partially Supports Debugging states such as Started, Stopped, Paused, and Resumed that are implied visually in Visual Studio, are not exposed programmatically to assistive technology. Customers relying on screen readers will not receive notifications that debugging has started, stopped, or entered break state. Users can read Visual Studio's title bar to determine if debugging is active or not - "Debugging" will be in the title if debugging. To determine if the debugged application is in break mode, look for the "Show Next Statement" menu item in the Debug top level menu - if it is present, the debugger is in a break state.When a “No Symbol Loaded” page is shown when the user hit a break, the user can add path to the symbol search path box. There are suggestions in the dropdown when the user types in the path. However, screen reader doesn’t announce the suggestions. The users rely on screen reader will not get notified about the notification. However, users can use arrow up/down keys to navigate the suggestions in the dropdown. Screen reader will announce the item.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.There are several different accessibility issues with the Pull Members Up dialog which is a new Roslyn code refactoring. For instance screen readers would read internal namespace information for members listed in the dialog.When the user inspects the Modules window in debugging, the screen reader doesn't announce the sorting action that're performed on the table. It doesn't read the header for the cell value in the table.When the user uses search in Locals, Autos, and Watch window, the user may not know that the search has a dropdown via assistive technology.Screen reader doesn't read the second column in Autos, Locals, and Watch window.
1.3.2 Meaningful Sequence A Partially Supports When the user uses advanced navigation in Narrator on the table in the Modules window, the Narrator focus is not logical while navigating using CAPS+Arrow keys.When the user uses Narrator in scan mode on Autos, Locals, and Watch window, the Narrator doesn't read the content in a meaningful way.
1.3.3 Sensory Characteristics A Supports
1.3.4 Orientation AA Not Evaluated
1.3.5 Identify Input Purpose AA Not Evaluated
1.4.1 Use of Color A Supports
1.4.2 Audio Control A Not Applicable
1.4.3 Contrast (Minimum) AA Partially Supports In the Xamarin iOS Simulator, the color contrast of many of the controls may make it difficult for some users to read text or see controls. Some icons on the VSTO FormRegion wizard do not meet High Contrast Standards
1.4.4 Resize text AA Supports
1.4.5 Images of Text AA Supports
1.4.10 Reflow AA Not Evaluated
1.4.11 Non-Text Contrast AA Not Evaluated
1.4.12 Text Spacing AA Not Evaluated
1.4.13 Content on Hover or Focus AA Not Evaluated
2.1.1 Keyboard A Partially Supports Inserting controls from the toolbox to the Xamarin Forms Previewer/Code Editor is not currently possible with only a keyboard.It is not currently possible to obtain keyboard focus on the Platform, Device, Orientation and Zoom controls on the Xamarin Forms Previewer. In the Xamarin iOS Simulator, many controls are inaccessible to keyboard-only users. In many cases in Visual Studio, users cannot use keyboard to show the tooltip of a control. 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 provider.
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.While inspecting a performance violation in an IntelliTrace file with performance data, users cannot use SHIFT+TAB to get out of the call tree once the focus is set on it. This is a keyboard trap for users with visual impairments who will find it difficult to navigate back from the call tree. However, the user can use TAB to get out of the call tree.Some users of the Xamarin Property Panel may experience a keyboard focus trap when navigating away from the search properties text view via tab navigation.In the Xamarin iOS Simulator, users may experience a keyboard focus trap in the zoom combo box.
2.1.4 Character Key Shortcuts A Not Evaluated
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 In the Xamarin iOS Simulator, the focus order is incorrect for some of the controls. This may lead to confusing behavior for users who attempt to tab-navigate while using the Xamarin iOS Simulator. The keyboard focus is not correct in the Select Data Source Window Keyboard focus order is incorrect under the Debug tab in the project properties window. The focus loops within the Debug tab.
2.4.4 Link Purpose (In Context) A Supports
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 When opening a memory heap analysis window from either the Diagnostic Tool Window's memory tool or the Debug Managed Memory dump debugging feature, the initial keyboard focus is set to a parent container that has the narrative text of the path to a file on disk. This will also happen when selecting a snapshot to diff against, or when the user tabs off of the last element in the view. This focus element can be disorienting to users, as they are not alerted to where the tool has taken them. In the meantime, pressing tab will return focus to the tool as expected.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.
2.5.1 Pointer Gestures A Not Evaluated
2.5.2 Pointer Cancellation A Not Evaluated
2.5.3 Label in Name A Not Evaluated
2.5.4 Motion Actuation A Not Evaluated
3.1.1 Language of Page A Supports
3.1.2 Language of Parts AA Not Applicable
3.2.1 On Focus A Supports
3.2.2 On Input A Supports
3.2.3 Consistent Navigation AA Not Applicable
3.2.4 Consistent Identification AA Supports
3.3.1 Error Identification A Supports
3.3.2 Labels or Instructions A Supports
3.3.3 Error Suggestion AA Supports
3.3.4 Error Prevention (Legal, Financial, Data) AA Supports
4.1.1 Parsing A Partially Supports While inspecting a .NET allocation profiling report, users who rely on Narrator will not be able to interact with the application after unchecking/checking a context menu item.
4.1.2 Name, Role, Value A Partially Supports Some controls on the Xamarin Forms Previewer do not have names that can be programmatically determined. Some elements of the Xamarin Property Panel have children with non-unique names and may be difficult to differentiate for visually-impaired users. Users who rely on Assistive Technologies may have difficulties using Workflow Designer Property Panel.Users who rely on Assistive Technologies may have difficulties using the Query Builder dialog.Users who rely on Assistive Technologies may have difficulties using the Access Permission list items on the Data Link Properties dialog.Users who rely on Assistive Technologies may have difficulties using Table Adapter Configuration Wizard.Users who rely on Assistive Technologies may have difficulties using Data Source Configuration Wizard.While inspecting a performance report from the profiler, some UI elements have poor values for accessibility properties. Data tables in the report aren't defined as tables, and expandable items in the report aren't defined as expandable, for example. Screen reader users will be unable to determine the state or nature of all the elements in the report.While inspecting the Diagnostic Tools window, focus can be set to one of two invisible elements in the window which both have long values for the Name property of each element. The values in each Name property include the full path to a file on disk ("file://C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\ IDE\ CommonExtensions\Platform\ DiagnosticsHub\ WebViews\ Performance DebuggerSwimLanesView.html" for example). Screen readers will ready the lengthy text of the Name property which is not related to the contents of the window. While inspecting a performance report from the profiler, some UI elements have poor values for accessibility properties. Data tables in the report aren't defined as tables, and expandable items in the report aren't defined as expandable, for example. Screen reader users will be unable to determine the state or nature of all the elements in the report.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.Users who rely on Assistive Technologies may have difficulties using the ASP.NET ListViewControl.
4.1.3 Status Messages AA 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 March 18, 2019. 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.