Azure Batch AI
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
- 16
- Partially supports
- 3
- Does not support
- 0
- Not applicable
- 6
- Not evaluated
- 0
Level AA — 13 criteria
- Supports
- 9
- Partially supports
- 1
- Does not support
- 0
- Not applicable
- 3
- 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 | There are instances where screen reader does not read table information correctly on some blades. For example, Narrator is not reading any table structure information correctly on cluster nodes blade, Unmanaged file systems blade and Search editable showing on 'Batch AI file servers' blade. This happens on Edge/Firefox browser with Narrator/NVDA screen reader. |
| 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 | |
| 1.4.3 | Contrast (Minimum) | AA | Supports | |
| 1.4.4 | Resize text | AA | Supports | |
| 1.4.5 | Images of Text | AA | Supports | |
| 2.1.1 | Keyboard | A | Partially Supports | There are instances where some elements can't be accessed via keyboard. For example, in the Azure file share reference blade, when a new row is added, this new row can't be accessed through keyboard unless the header checkbox is selected. Another example is in overview blade, the column headers in the table is not accessible via keyboard. This happens only on Edge/Firefox browser |
| 2.1.2 | No Keyboard Trap | 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 | Supports | |
| 2.4.2 | Page Titled | A | Supports | |
| 2.4.3 | Focus Order | A | Supports | |
| 2.4.4 | Link Purpose (In Context) | A | Supports | |
| 2.4.5 | Multiple Ways | AA | Supports | |
| 2.4.6 | Headings and Labels | AA | Partially Supports | There are instances where menu header is not being read by screen reader in Edge/Firefox browser. For example, in home page, 'Resources' menu group header won't be read by Narrator/NVDA screen reader. |
| 2.4.7 | Focus Visible | AA | Supports | |
| 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 | Supports | |
| 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 | Supports | |
| 4.1.2 | Name, Role, Value | A | Partially Supports | There are instances where screen reader does not read some messages. For example, on Unmanaged file systems blade, Narrator doesn't providing the information about the message displayed under Mount and Relative mount path columns. This happens on Edge/Firefox browser with Narrator/NVDA screen reader. Another example is that screen reader NVDA does not read the role of 'Add' and 'Delete' control. This happens only on Firefox with NVDA. |
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 19, 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.