Customer and Partner Identity Management
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
- 22
- Partially supports
- 4
- Does not support
- 0
- Not applicable
- 4
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 15
- Partially supports
- 3
- Does not support
- 0
- Not applicable
- 2
- 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 | 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 | Fully supported when using newer unified sign-up/sign-in policy. Exception for legacy sign-in policies: * 1 page has limitations with screen reader indicating field is required |
| 1.3.2 | Meaningful Sequence | A | Supports | |
| 1.3.3 | Sensory Characteristics | A | Partially Supports | In a few cases instructions do not rely solely on sensory characteristics. Sensory characteristics include shape, location, size, orientation, and sound. |
| 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 | Supports | Fully supported when using newer unified sign-up/sign-in policy. Exception for legacy sign-in policies: * 1 page's error text luminosity ratio |
| 1.4.4 | Resize text | AA | Supports | |
| 1.4.5 | Images of Text | AA | Supports | |
| 1.4.10 | Reflow | AA | Partially Supports | In a few cases content cannot be presented without loss of information or functionality, and without requiring scrolling in two dimensions for vertical and horizontal scrolling. |
| 1.4.11 | Non-Text Contrast | AA | Partially Supports | In a few cases the visual presentation of user interface component and graphical objects do not have a contrast ratio of at least 3:1 against adjacent color(s). |
| 1.4.12 | Text Spacing | AA | Supports | |
| 1.4.13 | Content on Hover or Focus | AA | Supports | |
| 2.1.1 | Keyboard | A | Supports | There are a few instances where content cannot be operated through a keyboard or keyboard interface alone. |
| 2.1.2 | No Keyboard Trap | A | Supports | |
| 2.1.4 | Character Key Shortcuts | A | Supports | |
| 2.2.1 | Timing Adjustable | A | Supports | |
| 2.2.2 | Pause, Stop, Hide | A | Supports | |
| 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 | In a few cases focus order that is aligned with the meaning or operation of the UI is not supported. |
| 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 | Supports | |
| 2.5.2 | Pointer Cancellation | A | Supports | |
| 2.5.3 | Label in Name | A | Supports | |
| 2.5.4 | Motion Actuation | A | Supports | |
| 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 | |
| 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 | In a few cases Assistive Technologies (AT) cannot gather information about, activate (or set) and keep up to date on the status of user interface controls in the content. |
| 4.1.3 | Status Messages | AA | Partially Supports | In a few cases content implemented using markup languages, status messages cannot be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. |
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 24, 2021. 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.