Dynamics 365 - Field Service - Connected Field Service
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
- 11
- Partially supports
- 10
- Does not support
- 0
- Not applicable
- 9
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 12
- Partially supports
- 5
- 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 (50)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Partially Supports | Screen reader does not read the icon image next to the Entitlement owner field. The icon does not handle any events. |
| 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 | - When adding an IoT Alert to a queue, the default or selected value in the dropdown is not announced by the screen reader. - When assigning IoT alert to a team or use, the screen reader does not read the tooltip for the look for records field. - When filtering IoT Alerts, the 'and/or' filter radio buttons are announced as independent controls, when they should be announced as a selection option.- When sending a Command to a device, the command input form does not have a label.- Narrator is not announcing the image behind "Connected Field Service Dashboard" combo box. - Incorrect control type exists for image beside the IoT Alert status on the work order form.- Connected Field Service breadcrumb in the header does not contain <ul> or <ol>.- Unable to access the sorting tab with keyboard while Narrator is on on the IoT Alerts screen.- Narrator is not announcing error as soon as error thrown by the "Name" field in the IoT Command form. |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | - Keyboard focus is not logical after clicking on the "close" button of the "Select a Record" pop-up.- Narrator tab focus does not go to the combo box present on the screen when selecting an Organization in the IoT Deployment app\. |
| 1.3.3 | Sensory Characteristics | A | Supports | |
| 1.3.4 | Orientation | AA | Supports | |
| 1.3.5 | Identify Input Purpose | AA | Supports | |
| 1.4.1 | Use of Color | A | Supports | |
| 1.4.2 | Audio Control | A | Not Applicable | |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | - Keyboard focus is not clearly visible on the "Created" buttons in the progress bar within IoT Alert. Additionally list item such as "Created " after applying high contrast Black and White mode on the same form. - More button is not visible after applying high contrast Black and White mode within IoT Alert page. |
| 1.4.4 | Resize text | AA | Partially Supports | When looking at 'Device Readings' for IoT devices in 200% resize the first two dates on x-axis are overlapping with each other and the last two dates are not visible. |
| 1.4.5 | Images of Text | AA | Supports | |
| 1.4.10 | Reflow | AA | Partially Supports | When changing display setting to 1280x1024 and Zoom the page to 400% in device readings the graph under device reading is not visible. |
| 1.4.11 | Non-Text Contrast | AA | Supports | |
| 1.4.12 | Text Spacing | AA | Supports | |
| 1.4.13 | Content on Hover or Focus | AA | Supports | |
| 2.1.1 | Keyboard | A | Partially Supports | Unable to access "More Commands" on TreeView control for Customer Assets with a keyboard. |
| 2.1.2 | No Keyboard Trap | A | Partially Supports | When focus is on Asset's tree control, user is unable to navigate to the previous control using "shift+tab". |
| 2.1.4 | Character Key Shortcuts | A | Not Applicable | |
| 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 | - Keyboard focus is not logical after clicking on the "close" button of the "Select a Record" pop-up in the Create IoT alert form. - Keyboard focus is navigated back to 'Look For Queue' after clicking on 'Search For All Records' button.- Keyboard Focus is moving to the background after last interactive link is presented in the Connected CFS flow page.- Keyboard focus is navigated back to 'User or team lookup' after clicking on 'All, Users, Teams' tabs in the Assign IoT alert prompt. |
| 2.4.4 | Link Purpose (In Context) | A | Supports | |
| 2.4.5 | Multiple Ways | AA | Supports | |
| 2.4.6 | Headings and Labels | AA | Supports | |
| 2.4.7 | Focus Visible | AA | Partially Supports | - Keyboard focus is not clearly visible on the "Created" buttons in the progress bar for an IoT alert.- Keyboard Focus is not clearly visible on list item such as "Created " after applying high contrast Black and White mode.- More button is not visible after applying high contrast Black and White mode in the IoT Alert form. |
| 2.5.1 | Pointer Gestures | A | Not Applicable | |
| 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.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 | Partially Supports | Narrator is not announcing error as soon as error thrown by the "Name" field in the IoT alerts form. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Commands form where user enters the command to be sent does not have a label. |
| 3.3.3 | Error Suggestion | AA | Supports | |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | |
| 4.1.1 | Parsing | A | Partially Supports | Not all ID attribute values in the IoT Alerts screen, audit history screen, or General incident form are unique. |
| 4.1.2 | Name, Role, Value | A | Partially Supports | Incorrect control type exist for image beside the "Aborted x days" ago text. |
| 4.1.3 | Status Messages | AA | Partially Supports | NVDA reads partially the status message for deployment app as "0/15 , 1/15 in progress" instead of "deploying services and components please wait while we create and deploy azure services 0/15 in progress" |
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 14, 2022. 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.