This article provides a checklist for digital accessibility for Power BI reports.
Detailed Information
Power BI and Tableau dashboards are not "conventional electronic documents" (PDF, Word, Excel, PowerPoint). They are treated as "web content." When the University provides or makes these dashboards available through a web-based platform, they must conform to WCAG 2.1 Level AA by the April 2026 compliance date.
Because dashboards are interactive, alt text is only one piece. In practice, accessibility depends on whether someone can operate the dashboard by keyboard and understand the information without relying on vision. When the University uses digital technology as part of a course, program, or other activity, an Information Technology Review must be completed.
Implementation notes/ examples
Common areas to check include the following.
Keyboard navigation and focus order:
Keyboard access is a common failure point, including cases where users can get stuck in a visual or cannot reach key controls.
- Logical tab order: Ensure the Tab key moves through content in a sensible reading order (for example: Title → Filters → Main KPI → Chart 1 → Chart 2). Use available platform features (such as tab order or object ordering) to set and verify the sequence.
Meaningful data alternatives:
Screen readers often cannot interpret complex visuals (maps, scatter plots, dense charts) without an equivalent representation of the data.
- Accessible data tables: Ensure users can access the underlying data in a readable table, with clear headers and meaningful labels.
- Summary narratives: Add a short text summary that explains the takeaway (not just "bar chart of sales"), especially when the insight is not obvious from the table alone.
Sensory characteristics and color:
Do not use color as the only way to communicate meaning (WCAG 1.4.1).
- Markers and labels: Use patterns, markers, and text labels so series and categories are distinguishable without color.
- Non-text contrast: Ensure chart elements, boundaries, and icons have sufficient contrast against the background and adjacent colors (4.5:1 for normal text, 3:1 for large text). Use a contrast checker such as WebAIM.
- Avoid directional instructions: Avoid "see the chart on the right." Use descriptive titles and labels instead.
Interactions and slicers:
Filters and interactive controls are another common failure point.
- Standard controls: Prefer standard dropdowns and list filters over custom click-to-filter interactions when possible.
- Labeling: Every filter/control needs a clear, programmatically associated label so screen reader users know what they are filtering and what values are available.
If an interactive dashboard cannot be made accessible, provide an equally effective accessible alternative that delivers the same information (for example, an accessible data table plus a short narrative summary of key takeaways).
Environment
- Power BI and other data visualization tools