ACR Index Get a draft ACR

Azure Tools Storage Explorer

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.

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

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.3.1 Info and Relationships A Partially Supports 1. Screen readers may not automatically read the contents of newly opened dialogs. Users may need to navigate the dialog to discover all available content.
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
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, 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.3. On macOS, there is no official standard for what keyboard shortcut should open the context menu, and Electron does not support any sort of unofficial standard. Thus, users on macOS will not be able to open the context menu.4. NVDA has been known to sometimes change the focus without any user input/programmable change of focus.
2.1.2 No Keyboard Trap A Supports
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 Supports
2.4.4 Link Purpose (In Context) A Supports
2.5.1 Pointer Gestures A Not Applicable
2.5.2 Pointer Cancellation A Not Applicable
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.2.1 On Focus A Supports
3.2.2 On Input A Supports
3.3.1 Error Identification A Supports
3.3.2 Labels or Instructions A 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. Screen readers may affect keyboard navigation on the data grid on the right hand side (file list, blob list, table entity list, queue messages list). They may also interact poorly with the data grid on the right hand side.4. Some native Windows dialogs do not meet accessibility standards.5. Date time controls are not fully screen reader accessible.6. VoiceOver announces the incorrect information when navigating elements in the tree view.7. 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.8. Screen readers might say the wrong thing when focusing buttons inside of tabs (Close Tab and Keep Tab Open).9. Screen readers might not give a fully accessible description of tabs10. JAWS does not read the contents of dropdowns.11. VoiceOver may announce the address bar/breadcrumb bar on the right hand side as editable when it is actually not.12. NVDA does only announces the collapsed state of tree items in the resource tree while expanding or collapsing them.13. JAWS does not announce the level of tree items.14. Depending on your settings, JAWS and NVDA might announce the address bar/breadcrumb bar on the right hand side as editable or blank when it is actually not.15. 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.).16. Tooltips are not read by screen readers.17. 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. Screen readers may affect keyboard navigation on the data grid on the right hand side (file list, blob list, table entity list, queue messages list). They may also interact poorly with the data grid on the right hand side.4. Some native Windows dialogs do not meet accessibility standards.5. Date time controls are not fully screen reader accessible.6. VoiceOver announces the incorrect information when navigating elements in the tree view.7. 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.8. Screen readers might say the wrong thing when focusing buttons inside of tabs (Close Tab and Keep Tab Open).9. Screen readers might not give a fully accessible description of tabs.10. JAWS does not read the contents of dropdowns11. VoiceOver may announce the address bar/breadcrumb bar on the right hand side as editable when it is actually not.12. NVDA does only announces the collapsed state of tree items in the resource tree while expanding or collapsing them.13. JAWS does not announce the level of tree items.14. Depending on your settings, JAWS and NVDA might announce the address bar/breadcrumb bar on the right hand side as editable or blank when it is actually not.15. 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.).16. Tooltips are not read by screen readers.17. VoiceOver sometimes focuses button labels. These should not be focused.
1.2.4 Captions (Live) AA Not Applicable
1.2.5 Audio Description (Prerecorded) AA Not Applicable
1.3.4 Orientation AA Supports
1.3.5 Identify Input Purpose AA Supports
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. The highlight text in some text boxes may be inappropriately themed 5. 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.
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 Supports
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.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, 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. On macOS, there is no official standard for what keyboard shortcut should open the context menu, and Electron does not support any sort of unofficial standard. Thus, users on macOS will not be able to open the context menu.4. NVDA has been known to sometimes change the focus without any user input/programmable change of focus.5. Focusing the app menu and context menus does not always trigger focus events.6. Keyboard focus/ordering is inconsistent in the Microsoft authentication windows (where you enter your username and password).7. Not all of the controls inside of date time controls are focusable.8. Focus may not always immediately go to context menus. You may have to use the arrow keys to establish focus.9. 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.10. You can not keyboard focus error icons that appear next to placeholder tree elements when creating a new resource in the resource tree.11. The links in the address bar/breadcrumb bar on the right hand side are not keyboard focusable.12. There is a loss of focus right before focusing the table headers for the data grid on the right hand side.13. There are no keyboard shortcuts to quickly navigate between panes.14. On macOS, focus does not always automatically go to dialogs.
3.1.2 Language of Parts AA Not Applicable
3.2.3 Consistent Navigation AA Supports
3.2.4 Consistent Identification AA Supports
3.3.3 Error Suggestion AA Supports
3.3.4 Error Prevention (Legal, Financial, Data) AA Supports
4.1.3 Status Messages AA Supports
1.2.6 Sign Language (Prerecorded) AAA Not Evaluated
1.2.7 Extended Audio Description (Prerecorded) AAA Not Evaluated
1.2.8 Media Alternative (Prerecorded) AAA Not Evaluated
1.2.9 Audio-only (Live) AAA Not Evaluated
1.3.6 Identify Purpose AAA Not Evaluated
1.4.6 Contrast (Enhanced) AAA Not Evaluated
1.4.7 Low or No Background Audio AAA Not Evaluated
1.4.8 Visual Presentation AAA Not Evaluated
1.4.9 Images of Text (No Exception) AAA Not Evaluated
2.1.3 Keyboard (No Exception) AAA Not Evaluated
2.2.3 No Timing AAA Not Evaluated
2.2.4 Interruptions AAA Not Evaluated
2.2.5 Re-authenticating AAA Not Evaluated
2.2.6 Timeouts AAA Not Evaluated
2.3.2 Three Flashes AAA Not Evaluated
2.3.3 Animation from Interactions AAA Not Evaluated
2.4.8 Location AAA Not Evaluated
2.4.9 Link Purpose (Link Only) AAA Not Evaluated
2.4.10 Section Headings AAA Not Evaluated
2.5.5 Target Size AAA Not Evaluated
2.5.6 Concurrent Input Mechanisms AAA Not Evaluated
3.1.3 Unusual Words AAA Not Evaluated
3.1.4 Abbreviations AAA Not Evaluated
3.1.5 Reading Level AAA Not Evaluated
3.1.6 Pronunciation AAA Not Evaluated
3.2.5 Change on Request AAA Not Evaluated
3.3.5 Help AAA Not Evaluated
3.3.6 Error Prevention (All) AAA 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 December 16, 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.