A repo consolidating accessibility resources for Power BI.
Principle 1: Perceivable - Information and user interface components must be presentable to users in ways they can perceive.
| Number | Title | Guideline |
|---|---|---|
| 1.1 | Text Alternatives | 🔗 Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. |
| 1.2 | Time-based Media | 🔗 Provide alternatives for time-based media. |
| 1.3 | Adaptable | 🔗 Create content that can be presented in different ways (for example simpler layout) without losing information or structure. |
| 1.4 | Distinguishable | 🔗 Make it easier for users to see and hear content including separating foreground from background. |
Principle 2: Operable - User interface components and navigation must be operable.
| Number | Title | Guideline |
|---|---|---|
| 2.1 | Keyboard Accessible | 🔗 Make all functionality available from a keyboard. |
| 2.2 | Enough Time | 🔗 Provide users enough time to read and use content. |
| 2.3 | Seizures | 🔗 Do not design content in a way that is known to cause seizures. |
| 2.4 | Navigable | 🔗 Provide ways to help users navigate, find content, and determine where they are. |
Principle 3: Understandable - Information and the operation of user interface must be understandable.
| Number | Title | Guideline |
|---|---|---|
| 3.1 | Readable | 🔗 Make text content readable and understandable. |
| 3.2 | Predictable | 🔗 Make Web pages appear and operate in predictable ways. |
| 3.3 | Input Assistance | 🔗 Help users avoid and correct mistakes. |
Principle 4: Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
| Number | Title | Guideline |
|---|---|---|
| 4.1 | Compatible | 🔗 Maximize compatibility with current and future user agents, including assistive technologies. |
🔗 Microsoft Learn: Report Accessibility Checklist
All Visuals
- Ensure color contrast between title, axis label, and data label text and the background are at least 4.5:1.
- Avoid using color as the only means of conveying information. Use text or icons to supplement or replace the color.
- Replace unnecessary jargon or acronyms.
- Ensure alt text is added to all non-decorative visuals on the page.
- Check that your report page works for users with color vision deficiency.
Slicers
- If you have a collection of several slicers on your report pages, ensure your design is consistent across pages. Use the same font, colors, and spatial position as much as possible.
Textbox
- Ensure color contrast between font and background are at least 4.5:1.
- Make sure to put text contents in the alt text box so screen readers can read them.
Visual interactions
- Is key information only accessible through an interaction? If so, rearrange your visuals so they're pre-filtered to make the important conclusion more obvious.
- Are you using bookmarks for navigation? Try navigating your report with a keyboard to ensure the experience is acceptable for keyboard-only users.
Sort order
- Have you purposefully set the sort order of each visual on the page? The accessible Show Data table shows the data in the sort order you have set on the visual.
Tooltips
- Don't use tooltips to convey important information. Users with motor issues and users who don't use a mouse will have difficulties accessing them.
- Do add tooltips to charts as ancillary information. It's included in the accessible Show Data table for each visual.
Video
- Avoid video that automatically starts when the page is rendered.
- Ensure your video has captions, or provide a transcript.
Audio
- Avoid audio that automatically starts when the page is rendered.
- Provide a transcript for any audio.
Shapes
- Make sure any decorative shapes are marked as hidden in tab order, so they aren't announced by a screen reader.
- Avoid using too many decorative shapes to the point where they're distracting.
- When using shapes to call out data points, use alt text to explain what is being called out.
Images
- When using images to call out data points, use alt text to explain what is being called out.
- Make sure any decorative images are marked as hidden in tab order, so they aren't announced by a screen reader.
- Avoid using too many decorative images, to the point where they're distracting.
Power BI visuals
- Check the accessible Show Data table for Power BI visuals. If the information shown isn't enough, look for another visual.
- If you use the Play Axis custom visual, ensure it doesn't auto play. Make it obvious that the user must press the play/pause button to start/stop the changing values.
Across visuals on the page
- Set tab order and turn off tab order (mark the item as hidden) on any decorative items.
Kerry Kolosko has a wonderful article on considerations for people that have vestibular conditions.
I have made a number of M functions that help deal with colors and consider color blindness.
Microsoft MVP Bernat Agulló Roselló has some great articles on using DAX and Tabular Editor to deal with colors:
🔗 A DYNAMIC COLOR GRADIENT FOR VALUES AND TOTALS
🔗: BUILDING A FADING BAR CHART
🔗: THEME-COMPLIANT CONDITIONAL FORMATTING MEASURES
🔗 Web Content Accessibility Guidelines (WCAG) 2.0
🔗 Laws of UX
🔗 Microsoft Learn: Design Power BI reports for accessibility
🔗 Microsoft Learn: Keyboard Shortcuts for Power BI