Movere
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
- 16
- Partially supports
- 8
- Does not support
- 0
- Not applicable
- 6
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 9
- Partially supports
- 7
- Does not support
- 0
- Not applicable
- 4
- 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 | User Experience:- User will find difficulty to identify the image control if that image control doesn’t have alt text. |
| 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 | User Experience:- Screen reader user would be confused if screen reader doesn't associate column header with its row cell value as user won't understand the table properly and they won't know about the respective column headers.- Screen reader user will be affected if they don’t find any cell value respect to that search column header. It will be good if end user have search functionality within the column header to filter out. - Screen reader user won't get state of any control if screen reader doesn't provides state for that control and they might get confused for such control. Not only this, they won't be able to proceed further because of such confusion.- Screen reader user won't get search suggestion if that suggestion list is not being announced by screen reader and user will have to navigate manually, which will consume user's time and effort. Not only this, they will not get an idea that input given by them is validating the correct data or not.- Screen reader user will be affected if screen reader doesn't provide placeholder text as user won't be able to proceed with the next one if they skip any required field.- Users using screen reader might get confused and not able to interact with the element properly if screen reader is not reading the column name along with header.- Screen reader will be affected if screen reader doesn't announce sorting information at table as user won't know that there is sorting functionality and they won't fetch data sorted.- Screen Reader users will get impacted if screen reader does not provide any information about the device selection or deselection then users who rely on screen reader will not able to get the complete information searched list elements.- Screen reader user will be affected if screen reader doesn't announce information about the charts as user won't be able to find out the information and might miss the functionality. |
| 1.3.2 | Meaningful Sequence | A | Supports | |
| 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 | User Experience:- Blind or low vision user will find difficulty to see the control or element if there is insufficient color contrast; user won't be able to perform functionality over such control. |
| 1.4.4 | Resize text | AA | Partially Supports | User Experience:- User will find difficulty to see the control if controls are not visible after resizing text to 200%; user won't be able to perform functionality over such control. |
| 1.4.5 | Images of Text | AA | Supports | |
| 1.4.10 | Reflow | AA | Partially Supports | User Experience:- User will find difficulty to interact with controls if controls are not visible after resizing to 400%: user won't be able to proceed further. |
| 1.4.11 | Non-Text Contrast | AA | Partially Supports | User Experience:- Blind or low vision user will find difficulty to see the non text control if that control or element has insufficient color contrast ratio; user won't be able to proceed further. |
| 1.4.12 | Text Spacing | AA | Supports | |
| 1.4.13 | Content on Hover or Focus | AA | Partially Supports | User Experience:- The keyboard users with low vision will find it difficult to see it when text spacing is applied. The users will not be able to see the controls and text if it hidden or overlapped. - User will be affected if tooltip content is not accessible by mouse hover while user hovers on any tool tip as user won't able to read content and navigate to it. |
| 2.1.1 | Keyboard | A | Partially Supports | User Experience:- User will find difficulty to interact with the control if that control is not accessible through keyboard. This will impact the functionality of relevant control and also won't be able to perform the desired functionality over such control. - Keyboard dependent users will face difficulty if the control elements are not accessible by using keyboard. User who is dependent on keyboard will not able to perform the functionality of that control, so the end users will get confused and this may lead to disorientation.- User would be affected to identify the controls if controls are not accessible by double tap and they won't be able to perform an action on desired element, which is having some information.- If there is no visual label and there is no tool tip appearing on the control element by using keyboard, then end users won't be able to identify what the icon is actually for.- Users who rely on keyboard will find difficulty to identify the purpose of visual icon if tooltip is not visible for that visual icon. Not only this, they won't be able to get the context of such controls and won't be able to perform functionality over that control.- Users depending on keyboard might get affected as Sorting button is not accessible with swipe navigation present with column header on “Device list” page, which may impact the efficiency of the user. |
| 2.1.2 | No Keyboard Trap | A | Partially Supports | User Experience: - Users depending on keyboard might get affected as focus is getting trapped at the last column header of the table on “Device list” page which may impact the efficiency of the user. User will not be able to navigate to the table row and further on the page. |
| 2.1.4 | Character Key Shortcuts | 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 | Partially Supports | User Experience: - Users depending on keyboard might get affected as TalkBack focus order is not in sequential order while navigating on screen.- User might get affected if focus order is not logical or doesn't flow sequentially.- Users depending on keyboard might get affected as Focus is moving to hidden element on Overview screen. |
| 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 | User Experience: - User will be misguided if h1 tag is defined for any control appearing over dialog screen as user might consider that control or dialog screen represent main topic or element of page. |
| 2.4.7 | Focus Visible | AA | Partially Supports | User Experience:- User will find difficulty to see any control if keyboard focus is not visible on any interactive control. |
| 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 | Not Applicable | |
| 3.2.1 | On Focus | A | Partially Supports | User Experience:- Users who rely on keyboard might get affected if keyboard focus does not land on interactive control after performing desire action and also user won't be able to get the flow of application as it will consume user's time and efforts to reach the expected screen. |
| 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 | Partially Supports | User Experience:- If instructions or labels do not clearly identify the controls in a form, the users will not know what input data is expected. The pages will look cluttered with unnecessary information and people with disabilities will miss important cues and instructions. |
| 3.3.3 | Error Suggestion | AA | Supports | |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | |
| 4.1.1 | Parsing | A | Supports | |
| 4.1.2 | Name, Role, Value | A | Partially Supports | User Experience:- User would find difficulty to identify the controls if name and role are not defined for any control as user won't get the context of that control and also they will skip the functionality relevant to that control.- Screen reader user will be affected if aria-label is not defined for any control as user won't get the purpose of control and also won't be proceed further.- Name is the fundamental property of the UI component if the presence of name is not there for any UI component then user who rely on screen reader will not able to know about the name of the UI component so the end users will get confused and not able to know the name of that control. |
| 4.1.3 | Status Messages | AA | Supports |
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 September 14, 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.