ACR Index Get a draft ACR

Azure Synapse tools

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

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 - Some information, structure, and relationships may not be fully conveyed in a way that assistive technologies can interpret.- Users relying on text or programmatic cues might experience challenges understanding certain content or layout relationships.
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 - Most features can be operated using a keyboard without time constraints on keystrokes.
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 Partially Supports - Keyboard focus generally follows a logical order aligned with the interface, though in some cases it may move to elements that are not visible.
2.4.4 Link Purpose (In Context) A Supports
2.5.1 Pointer Gestures A Supports
2.5.2 Pointer Cancellation A Supports
2.5.3 Label in Name A Partially Supports - Some user interface components may have names that do not fully include the visible text of their labels, which could affect clarity for assistive technologies.- Ensuring that the visible label text appears at the start of the component name supports better understanding and navigation.
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.2.6 Consistent Help A Supports
3.3.1 Error Identification A Supports
3.3.2 Labels or Instructions A Supports
3.3.7 Redundant Entry A Supports
4.1.1 Parsing A Not Applicable
4.1.2 Name, Role, Value A Partially Supports ensures that every UI control exposes its Name, Role, and Value programmatically so assistive technologies (screen readers, Braille, etc.) can correctly identify and interact with elements.
1.2.4 Captions (Live) AA Not Applicable
1.2.5 Audio Description (Prerecorded) AA Not Applicable
1.3.4 Orientation AA Not Applicable
1.3.5 Identify Input Purpose AA Supports
1.4.3 Contrast (Minimum) AA Partially Supports - Text and images of text generally meet contrast requirements for readability.- Some instances of smaller text or interface elements may have contrast levels that could be improved for better visibility.
1.4.4 Resize text AA Partially Supports - Text can be resized up to 200% without losing content or functionality, supporting users who need larger text for readability.
1.4.5 Images of Text AA Supports
1.4.10 Reflow AA Partially Supports - Content generally supports single-direction scrolling without loss of information or functionality.- Some areas with complex layouts, such as data tables or interactive elements, may require two-dimensional scrolling to maintain clarity and usability.
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 - Keyboard users can generally identify which element has focus, though in some areas the focus indicator could be more prominent to enhance visibility and ease of navigation.
2.4.11 Focus Not Obscured (Minimum) AA Supports
2.5.7 Dragging Movements AA Supports
2.5.8 Target Size (Minimum) AA Supports
3.1.2 Language of Parts AA Supports
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
3.3.8 Accessible Authentication (Minimum) AA Supports
4.1.3 Status Messages AA Partially Supports - Status messages are designed to be recognized by assistive technologies without requiring users to shift focus, enhancing seamless communication of updates and alerts.
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.4.12 Focus Not Obscured (Enhanced) AAA Not Evaluated
2.4.13 Focus Appearance 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
3.3.9 Accessible Authentication (Enhanced) 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 March 12, 2026. 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.