Dynamics 365 Customer Engagement - Portal
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
- 8
- Does not support
- 0
- Not applicable
- 6
- Not evaluated
- 5
Level AA — 20 criteria
- Supports
- 10
- Partially supports
- 1
- 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 | 1. For CK Editor, JAWS reads last list item (More Colors …) along with first list item(Automatic) for controls - "Text Color and Background color" inside "Colors" toolbar of CK Editor.2. JAWS reads some random values along with the name of the control on "color" and "Styles" comboboxes. It reads JavaScript … left parent.3. Screenreader does not read the name of the "Automatic" color that is selected for "Text Color" and "Background Color" controls of CK Editor.4. Screen Reader focus is not shifting to the "Choose File" control (for SharePoint Document management) after first iteration.5. Screen Reader is not reading the error messages in the "Add File" pop-up (for SharePoint Document management).6. Screen Reader is reading "Idea Submission Policy" instead of "New Idea Policy" in "Idea Forum".7. In PowerApps portal studio, if user chooses to fill RGBA values in color picker, then the inputs are announced in table format.8. In PowerApps portal studio, in form properties, the success message placeholder is not read through screen reader.9. In PowerApps portal home page, search toolbar ARIA roles does not contain particular children. |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Keyboard focus order is not logical for the grid present under the Entity Form Metadata. |
| 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 | In PowerApps Portal studio, the code editor text to assign a value to attribute has luminosity ratio less than 4.5:1 (it is 4:1). |
| 1.4.4 | Resize text | AA | Partially Supports | Tooltip shown on Alt + F1 keypress on Monaco editor is not properly visible in 200% zoom. The text of the tooltip is as follows:"<Line Number>, <Column Number> in a code editor- To configure the editor to be optimized for usage with a Screen Reader press Control+E now.- Pressing Tab in the current editor will insert the tab character. Toggle this behavior by pressing Control+M.- Press Control+H now to open a browser window with more information related to editor accessibility.You can dismiss this tooltip and return to the editor by pressing Escape or Shift+Escape." |
| 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 | 1. Keyboard focus order is not logical for the grid present under the Entity Form Metadata.2. Tool-tip doesn't appear when description field (rich text editor i.e. CK Editor) toolbar button receive keyboard focus3. In PowerApps Portal studio, if user tries to update colors, they can only do it through putting in hex code value but not through sliders in the color picker control.4. In PowerApps portal studio, if user edits text, the tooltip is not visible on keyboard focus for bold, italic and underline options.5. In PowerApps portal studio, user is not able to navigate to page options only through keyboard.6. In PowerApps portal studio, user will not able to view the tooltips on canvas components through keyboard navigation & in code editor as well, few tooltips can't be shown only through keyboard navigation. |
| 2.1.2 | No Keyboard Trap | A | Partially Supports | Keyboard focus order is not logical for the grid present under the Entity Form Metadata. |
| 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 | Partially Supports | PowerApps portal studio does not have "skip to main content" link enabling users to jump directly on canvas. |
| 2.4.2 | Page Titled | A | Partially Supports | 1. In dialog of "Quick Create: Account", the title is not read by Screen reader.2. In PowerApps Portal studio, the pages favicon and related title does not change with the navigation from PowerApps home to portal studio. |
| 2.4.3 | Focus Order | A | Partially Supports | Keyboard focus order is not logical for the grid present under the Entity Form Metadata. |
| 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 | Supports | |
| 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 | 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 | Screen Reader is reading "Idea Submission Policy" instead of "New Idea Policy" in "Idea Forum". |
| 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 | 1. For CK Editor, Buttons - Insert Image / Insert Table is not calling out aria label names while using screen reader.2. If you enter in CK editor, the base URL of org gets announced inappropriately.3. In PowerApps portal studio, if user creates a new page, then the new page dropdown does not announce the expanded state.4. In PowerApps portal studio, if user interacts with template dropdown in page properties, the template combo box does not announce the state and role of the combo box.5. In PowerApps portal studio, if user interacts with dropdowns in form properties, the form combo boxes do not announce the state and role of the combo box. |
| 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 April 4, 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.