Accessibility issue in Power BI report server 2023 for grouped elements

[sahil_tasgavkar]

Hi All,

We have recently upgraded our Power BI reporting server to Version1.16.8420.13742 (January 2023) . We are facing an issue regarding the tab order for report elements in the reporting server.
The tab order defined while developing the report in Power BI desktop (jan 2023) works as intended when the elements(slicers,text boxes etc.) are not grouped, In Desktop application, Power BI service and Reporting server.

However, when we have grouped elements the tab order doesn't work as intended and is random. In the desktop application and power Bi service it works fine but not in the reporting server.

Steps to replicate the scenario:

1. Page 1 with Individual elements present without any grouping, Tab order defined under selection view for individual elements
2. Page 2 with few elements logically grouped, Tab order defined under selection view for individual elements and groups.
3. Uploading the report to Power BI reporting server and using keyboard to navigate

Please could you help us on the same, on whether it's a known issue or any solution to resolve the same.

[sylwiasajdak]

To preface, I only have experience of making reports published to Power BI service and then shared using public url (not Power BI server). But I would discourage using groups as they aren't great for accessibility.

The main cases where I think groups make sense are for elements that won't be read by a screen reader or where a group makes logical sense (e.g. a filter or guidance panel where the user may want to skip over a number of elements).

If you do choose to use groups and have them be screen readable I would include clear guidance in the group alt text about how to enter the group e.g. "Press alt + enter here to open additional guidance about navigating this report". An element at the end of group detailing how to exit the group could also be useful to an end user e.g. 

"Press escape to exit this additional guidance".

Again, apologies since this doesn't directly address your question but you may want to reconsider if using groups is necessary / appropriate for your users' needs.