ACR Index Get a draft ACR

Azure Portal Framework (IbizaFx)

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 Partially Supports Decorative images should be hidden from assistive technologies so that screen readers do not move focus to or announce them. Only meaningful and informative content should be exposed through the accessibility tree, ensuring an efficient and seamless navigation experience for users of assistive technologies.
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 All user interface elements should be programmatically exposed with accurate semantic roles, descriptive accessible names, and appropriate relationships. Visual headings should be defined as headings programmatically, form controls should be properly associated with their labels, interactive elements should have meaningful accessible names, and graphical content should provide accessible information that conveys its purpose and context to users of assistive technologies.
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 All interactive elements within the Resource Compliance pie chart, including individual chart segments, should be keyboard accessible. Users should be able to navigate to, access, and interact with the chart segments using standard keyboard commands, with relevant information and functionality available to both keyboard and assistive technology users.
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 Not Applicable
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 Partially Supports The Start control should have a meaningful and descriptive accessible name that clearly communicates its purpose and functionality. This will ensure that users of assistive technologies can easily identify and understand the control without relying on surrounding visual context.
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 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 All interactive elements should expose accurate and complete accessibility properties, including appropriate control types, names, roles, and states. Any changes in control state should be communicated automatically to assistive technologies, ensuring that users receive equivalent information and feedback regardless of the method used to access the interface.
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 When the application is displayed in dark theme, the text "Recommended" does not provide sufficient contrast against its background. The observed luminosity contrast ratio is below the minimum required threshold, which may make the text difficult to perceive for users with low vision, color vision deficiencies, or those viewing content under challenging lighting conditions.
1.4.4 Resize text AA Supports
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 Partially Supports When text spacing settings are applied, all X-axis labels should remain fully visible, readable, and properly spaced without overlapping or truncation. The chart should adapt its layout to accommodate the modified text presentation while ensuring that all information remains accessible and understandable.
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 Supports
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 Not Applicable
3.3.8 Accessible Authentication (Minimum) AA Supports
4.1.3 Status Messages AA Partially Supports When search results are updated, screen readers should automatically announce relevant result information, such as the number of results returned or changes to the results list. This ensures that users of assistive technologies receive timely feedback and can effectively understand and interact with the search results.
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 August 26, 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.