Power BI e Acessibilidade

Experiência com o Power BI

O Power BI tem um conjunto de teclas de navegação pelos seus objetos que são específicas da aplicação. Por exemplo, se os utilizadores de leitores de ecrã não estiverem conscientes das mesmas vão provocar colisões entre as teclas de atalho de navegação do leitor de ecrã e do Power BI.

As teclas de navegação do Power BI são

Teclas	Ação
CTRL+Enter	Entra no Frame/Moldura do Power BI
TAB	Próximo Objeto
SHIFT+TAB	Objeto Anterior
Enter	Mergulha no Objeto
Escape	Vem à superfície do Objeto
Espaço	Seleciona/Desseleciona opção (checkbox)
seta baixo	Próximo elemento
seta cima	elemento anterior

Nota: as teclas de cursor (setas) nem sempre funcionam de forma consistente em todos os objetos e elementos. Apesar de fazerem algo similar a TAB e SHIFT+TAB, por vezes são capturadas pelos elementos para desempenhar outras funções.

Overview of accessibility in Power BI

https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-accessibility-overview

• Overview of accessibility in Power BI - Power BI
• Features and suggestions for creating accessible Power BI Desktop reports including Web Content Accessibility Guidelines (WCAG)

Creating accessible reports in Power BI - Power BI

https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-accessibility-creating-reports#report-accessibility-checklist

• Creating accessible reports in Power BI - Power BI
• How to create accessible Power BI Desktop reports

Power BI accessibility checklist

In addition to providing accessibility tools and functionality, Power BI provides the following checklist you can use when creating reports. This checklist helps ensure your reports are accessible, and available to the largest audience, before you publish it.

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 are 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 do not use a mouse will have difficulties accessing them.
• Do add tooltips to charts as ancillary information. It is 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 are 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 are distracting.

Power BI visuals

• Check the accessible Show Data table for Power BI visuals. If the information shown is not enough, look for another visual.
• If using the Play Axis custom visual, ensure it does not 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.

Considerations and limitations

There are a few known issues and limitations with the accessibility features. Descriptions of those issues and limitations are in the following list:

• When using screen readers with Power BI Desktop, you'll have the best experience if you open your screen reader before opening any files in Power BI Desktop.