ACR Index Get a draft ACR

Microsoft Azure Storage Explorer 1.16.0

Accessibility Conformance Report published by Microsoft

Partial extraction. We read 25 of 30 Level A and 15 of 20 Level AA criteria from this document (80% coverage). The remainder are missing from our extraction, not necessarily from Microsoft's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.

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.

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 (40)

Conformance as stated by Microsoft in its published report.
CriterionNameLevel ConformanceRemarks 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. NVDA and JAWS doesn't announce "expanded/collapsed" state for "Azure environments" combo box in Connect dialog.2. VoiceOver doesn't announce "expanded/collapsed" state for "Azure environments" combo box in Connect dialog.3. VoiceOver announces "number" input's control type as non-standard "stepper".4. VoiceOver doesn't read the label of the edit boxes in the Properties dialog when focusing them.5. VoiceOver doesn't announce the state change for "Hide Actions and Properties" control in Properties panel.6. VoiceOver doesn't announce Allowed methods edit box name in CORS dialog.7. NVDA announces checkbox labels twice in the Settings Panel.8. NVDA doesn't announce the value of the date in the date picker in Generate Shared Access Signature dialog.9. NVDA unnecessarily announcing "table" when focusing on Access Policy combo box in Get Shared Access Signature dialog.10. NVDA reads data table cells three times (focus can be set on cells right now).11. NVDA announces checkbox titles twice.12. JAWS unnecessarily announcing No button twice in Acquire Lease dialog.13. NVDA is reading the dialog title as row 1 column 1.14. VoiceOver announce the tree view as an "empty table".15. "Display name:" field in Attach to Local Emulator dialog is not announced by VoiceOver.
1.3.2 Meaningful Sequence A Supports
1.3.3 Sensory Characteristics A 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 1. The theme functionality in the "View" menu does not theme dropdowns, context menus, or the application's menus. You need to change the color theme of your OS to modify the colors of these menus.2. Dropdowns are not fully themed to follow high contrast standards.3. Calendars and date time pickers are not themed to follow high contrast standards.4. Native dialogs are not themed by the theme functionality in the "View" menu. To give these dialogs a high contrast theme, you need to change the color theme of your OS.5. "Info" icon does not meet minimum color contrast ratio of 3:1.
1.4.4 Resize text AA Partially Supports 1. Zooming in will work best with a screen resolution of 1280x1024 or higher.2. When zoomed in, you may have to resize the active window or use scrollbars to scroll content into view.3. The zoom functionality in the "View" menu does not zoom dropdowns, context menus, native dialogs, or the application's menus. The zooming of those UI elements is controlled by the OS.4. Zoom is tested up to 4x (200%).
1.4.5 Images of Text AA Supports
1.4.10 Reflow AA Partially Supports 1. At 400% zoom, controls(e.g. Open Connect Dialog, Settings, Send Feedback) present on left pane gets overlapped and controls present under Treeview panel are not visible
2.1.1 Keyboard A Partially Supports 1. In dialogs, you need to hit tab twice to get from the last control back to the first control. Additionally, OS'/screen readers sometimes choose to focus dialog windows instead of their first control when the dialogs are launched. If this happens, you can hit tab to move to the first control.2. In the main window, you need to hit tab twice to get from the last control back to the first control.
2.1.2 No Keyboard Trap 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 Partially Supports 1. NVDA is reading the dialogue title as row 1 column1
2.4.3 Focus Order A Partially Supports 1. Keyboard focus is lost after Cancel button in Configure Soft Delete Policy dialog.2. Keyboard focus goes into illogical order after Close control in Get Shared Access Signature dialog.3. Loss of keyboard focus is found after "Cancel" button in Configure Soft Delete Policy dialog.
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 1. In dialogs, you need to hit tab twice to get from the last control back to the first control. Additionally, OS'/screen readers sometimes choose to focus dialog windows instead of their first control when the dialogs are launched. If this happens, you can hit tab to move to the first control. In all cases, when the focus is on the window, the focus is not visible.2. In the main window, you need to hit tab twice to get from the last control back to the first control.3. Focusing the app menu and context menus does not always trigger focus events for Acc Event.4. Not all of the controls inside of date time controls are focusable5. Focus may not always immediately go to context menus. You may have to use the arrow keys to establish focus.6. The data grid on the right hand side is implemented as two separate tables. This is intentional, as it provides the ability to scroll the body of the table while also leaving the headers visible.7. Keyboard focus is not visible on the outer boundary of the "Create collection window" under Cosmos DB tree node.8. Loss of keyboard focus is found after "Cancel" button.
3.1.1 Language of Page A Supports Storage Explorer now supports 18 languages:CzechGermanEnglishSpanishFrenchHungarianItalianJapaneseKoreanDutchPolishPortuguese (Brazil)Portuguese (Portugal)RussianSwedishTurkishChinese (Simplified)Chinese (Traditional)
3.1.2 Language of Parts AA Supports Storage Explorer now supports 18 languages:CzechGermanEnglishSpanishFrenchHungarianItalianJapaneseKoreanDutchPolishPortuguese (Brazil)Portuguese (Portugal)RussianSwedishTurkishChinese (Simplified)Chinese (Traditional)
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 Partially Supports 1. This standard is not met when Narrator is used.2. Screen readers are not supported on Linux.3. Some native Windows dialogs do not meet accessibility standards.4. Date time controls are not fully screen reader accessible5. VoiceOver announces the incorrect information when navigating elements in the tree view.6. The data grid on the right hand side is implemented as two separate tables. This is intentional, as it provides the ability to scroll the body of the table while also leaving the headers visible.7. Screen readers might not give a fully accessible description of tabs.8. JAWS does not read the contents of dropdowns.9. NVDA, JAWS, and VoiceOver do not always reliably read out aria-alerts. These include alerts from activities in the activity log, and alerts from the state of the tree view (searching, search complete, invalid path, etc.).10. Tooltips are not read by screen readers. To learn about keyboard shortcuts, you can read our shortcut key documentation.11. VoiceOver sometimes focuses button labels. These should not be focused.
4.1.2 Name, Role, Value A Partially Supports 1. This standard is not met when Narrator is used.2. Screen readers are not supported on Linux.3. Some native Windows dialogs do not meet accessibility standards.4. Date time controls are not fully screen reader accessible5. VoiceOver announces the incorrect information when navigating elements in the tree view.6. The data grid on the right hand side is implemented as two separate tables. This is intentional, as it provides the ability to scroll the body of the table while also leaving the headers visible.7. Screen readers might not give a fully accessible description of tabs.8. JAWS does not read the contents of dropdowns9. NVDA, JAWS, and VoiceOver do not always reliably read out aria-alerts. These include alerts from activies in the activity log, and alerts from the state of the tree view (searching, search complete, invalid path, etc.)10. Tooltips are not read by screen readers. To learn about keyboard shortcuts, you can read our shortcut key documentation.11. VoiceOver sometimes focuses button labels. These should not be focused.
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 May 22, 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.