Azure IoT Preconfigured Solutions
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
- 12
- Partially supports
- 7
- Does not support
- 0
- Not applicable
- 6
- Not evaluated
- 5
Level AA — 20 criteria
- Supports
- 7
- Partially supports
- 4
- Does not support
- 0
- Not applicable
- 2
- Not evaluated
- 7
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)
| 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 | In certain popup screens, screen reader doesn't announce state of control. For example, when you click on a device, the screen reader doesn't announce that the 'Device details' popup is shown in the screen. |
| 1.3.2 | Meaningful Sequence | A | Supports | |
| 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 | Supports | |
| 1.4.4 | Resize text | AA | Partially Supports | In one case, 'Search devices' text is not properly visible in default screen view (100%) or greater under 'search device' edit field. |
| 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 | Certain elements in the screen are not accessible through Keyboard Navigation. For example, all radio buttons in 'New Rule' flyout, controls in 'Device Details' flyout are not accessible through Keyboard Navigation. |
| 2.1.2 | No Keyboard Trap | A | Partially Supports | Under rules table section, Keyboard focus gets trapped. |
| 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 | Supports | |
| 2.4.2 | Page Titled | A | Supports | |
| 2.4.3 | Focus Order | A | Partially Supports | When using keyboard navigation, Focus order is not in correct manner under 'Dashboard' tab. |
| 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 | Screen readers will not read headings for 'New rule' and 'SIM Management' flyouts since Headings are not defined for them. |
| 2.4.7 | Focus Visible | AA | Partially Supports | Keyboard focus is not visible on some controls. For example, Keyboard focus is not visible on multiple controls on 'New rule' and 'Device Details' popup screens. |
| 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 | Supports | |
| 3.2.1 | On Focus | A | Partially Supports | In certain cases, after a popup is closed, the focus doesn't come back to the element where it originally was before the popup was opened. For example, after selecting 'Close' button focus is not moving on 'Manage device group' button under 'Manage device group' pop up. |
| 3.2.2 | On Input | A | Supports | |
| 3.2.3 | Consistent Navigation | AA | Partially Supports | In dashboard page, focus indicator will not navigate to every cell under table with arrow keys and instead it will navigate with tag key. |
| 3.2.4 | Consistent Identification | AA | Supports | |
| 3.3.1 | Error Identification | A | Partially Supports | In certain popups, Screen reader does not announce the error message due to failed validation. For example, Screen reader doesn't announce the error message while navigating to 'enter device id' edit field under 'New Device' pop-up. |
| 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 | Name & role are not defined or incorrect for certain controls. For example, Name & role are not defined for 'Help icon' and incorrect role is defined for 'humidity, pressure & temperature' controls under 'Device details' pop up screen. |
| 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 August 18, 2020. 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.