Easy Power BI Dashboards Accessibility Statement

Conformance goal

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 (opens in new tab) at Level AA. These guidelines are the recognized standard for making web content more usable for people with a wide range of disabilities, including visual, motor, auditory, and cognitive differences. We treat AA as an ongoing target rather than a one-time certification, and we review the site as we add pages.

Measures we take

Accessibility is part of how this site is built, not an afterthought. Concretely, we:

• Use semantic HTML with proper landmarks and a logical heading order, so screen readers can navigate the page structure predictably.
• Keep the site keyboard operable: interactive elements such as menus, the FAQ accordion, and the contact form can be reached and used without a mouse, with a visible focus indicator and a skip-to-content link.
• Maintain sufficient color contrast for text and meaningful interface elements against their backgrounds, aiming to meet the AA contrast thresholds.
• Provide descriptive alt text for meaningful images and mark decorative graphics so assistive technology can ignore them.
• Build labelled, accessible forms, where each field has an associated label, helpful error messages, and clear focus styling.
• Respect user preferences such as reduced motion and avoid relying on color alone to convey information.

Known limitations

We want to be honest rather than claim perfection. We are aware of areas that may not yet fully meet Level AA, and we are working to improve them:

• Some third-party embeds and analytics scripts are outside our direct control and may not meet the same standard as our own markup.
• Interactive Power BI report previews and sample dashboards are rich, visual artifacts; while we describe them in surrounding text, the embedded visuals themselves may not be fully operable by every assistive technology. When we build reports, we follow Microsoft's Power BI accessibility guidance (opens in new tab) to improve keyboard and screen-reader support.
• As we publish new pages, individual elements may temporarily fall short of our target until our next review catches them.

If you encounter a barrier that is not listed here, we would genuinely like to know so we can fix it.

How to report a problem

If any part of this website is difficult to use, or you need information in a different format, please tell us through our contact form.

Please include the page address and a short description of the problem, and the assistive technology or browser you were using if you know it. We aim to acknowledge accessibility reports within one business day and will work with you on a reasonable timeline to resolve the issue or provide the content another way.

This statement was last reviewed in 2026 and is updated as the site changes.