Expose tab order as a property of visuals for keyboard navigation
Users that consume Power BI reports with keyboard navigation (including screen readers) can tab through the visuals on a report page, but the tab order seems to be the order in which the visual was placed on the page by the report designer. So if I make a page and put two charts on the bottom row, a title text box at the top left, and a table on the top row, that is the tab order. I would like to be able to change a property to make the tab order go from title to table to chart 1 on bottom row to chart 2 on bottom row. This would make the report more accessible/inclusive and allow me to guide the keyboard user through the story/information in the appropriate order.
The December release of Power BI Desktop has a ton of accessibility improvements, and control over the focus order is one of them. You can set this within the selection pane. Read all the details in the blog: https://powerbi.microsoft.com/en-us/blog/power-bi-desktop-december-2018-feature-summary/#tabOrder
Also, the tab order doesnt work on power bi service at all. It does ignore tab order that is defined at the desktop level.
Hello Amanda, The tab order is not working power bi service .Especially if I make a tab on slicer and If I wanted to select an item from the slicer, I wouldnt be able to make selection. I have a power bi report with slicer as a selection and I wouldnt be able to pick anything from the slicer using keyboard. This is not meeting the ADA compliance and user dont want to use the tool if its not ADA compliance.
Very useful idea.
This could be useful also during development in Power BI desktop. I use the TAB key to move the selection through visuals. This is particularly important when two visuals are very near each other or overlapped. Selecting one visual with the mouse is almost impossible. Without tab ordering, it requires a lot of TAB key presses to select the other visual.
Moreover, to make the life easier and faster for the user who develops, what about letting the user to keep the TAB key pressed and make the selection moving seamless through the various visuals? Now, the user has to press and release the TAB key for each single visual to select and this requires a lot of time when there are dozens of visuals in the page.
I believe this feature could help meet WCAG2.0 Guidelines 1.3.2 and 2.4.3.