Visual Studio 2017
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 — 25 criteria
- Supports
- 10
- Partially supports
- 7
- Does not support
- 0
- Not applicable
- 8
- Not evaluated
- 0
Level AA — 13 criteria
- Supports
- 6
- Partially supports
- 2
- Does not support
- 0
- Not applicable
- 5
- Not evaluated
- 0
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 (38)
| 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.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 | See Table 1 |
| 1.3.2 | Meaningful Sequence | A | Supports | |
| 1.3.3 | Sensory Characteristics | A | Partially Supports | - Users using Narrator to configure C++ packages on a Windows Server may encounter difficulty understanding the loading process. - Users who use screen readers to create database projects from existing databases will not be notified about the progress of the import database task, but users can still finish the task. - Users who use screen readers to design database tables will not be notified about the loading screen when opening the table designer, but users can still finish the task. |
| 1.4.1 | Use of Color | A | Supports | |
| 1.4.2 | Audio Control | A | Not Applicable | |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | See Table 2 |
| 1.4.4 | Resize text | AA | Supports | |
| 1.4.5 | Images of Text | AA | Supports | |
| 2.1.1 | Keyboard | A | Partially Supports | See Table 3 |
| 2.1.2 | No Keyboard Trap | A | Partially Supports | Diagnostics - 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 tab 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 away from the call tree using the keyboard. Users may escape the trap by closing the IntelliTrace file and re-opening it. |
| 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 | See Table 4 |
| 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 | See Table 5 |
| 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 | Text in the debugger registers window does not currently support reading by word or line in screen readers. Users must move the caret character by character to have the text read by a screen reader. |
| 4.1.2 | Name, Role, Value | A | Partially Supports | See Table 6 |
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 June 22, 2018. 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.