Power BI reports currently do not fully meet WCAG 2.2 AA requirements for Keyboard Accessibility (2.1.1). Some interactive elements, such as tooltips or information boxes for data visualizations that appear on mouse hover, cannot be accessed using a keyboard alone. While screen readers can read the content, keyboard-only users who do not use screen readers cannot access this information.
Impact: This creates a significant barrier for users who rely on keyboard navigation, preventing them from accessing all report content and functionality. It also means reports cannot achieve WCAG 2.2 AA compliance.
Request: Please enhance Power BI so that all interactive elements, including hover-triggered tooltips and information boxes, are fully operable via keyboard navigation. This change would help ensure Power BI content meets WCAG 2.2 AA standards and supports accessible digital services.
-
PeterDaniels
on:
Add a Git-tracked “resources” folder to Lakehouses
- eNieSee on: PBI - Improve Date slicer user experience
-
andyclap
on:
Add native Dev/Test/UAT/Prod semantic model compar...
- rceu_42 on: Spark high concurrency session sharing between dif...
-
frithjof_v
on:
Computed Columns in Fabric Data Warehouse
- GregoryFollens on: Message showing when a workspace is linked to a pa...
- AndrewPNZ on: Allow Gateway Admin members who are not Fabric Adm...
- KarenLGrube on: Allow copying conditional formatting from one cell...
-
LiLiu_Fabric
on:
Deployment Pipeline Run in Fabric monitor
-
andyclap
on:
PBIP: Add “Reload from Disk” to Power BI Desktop f...