Table that spans multiple pages within a Paginated Report - Problem with Accessible PDF Tagging

[bethwhitmer]

Hello, 

We are developing a paginated report containing a data table that is very long and spans multiple report pages. When we convert the report to "Accessible PDF", the PDF tags tree creates a separate <table> tag for EACH page that the table spans across. So for example, if the table spans 3 pages of the report, there are 3 separate <table> tags within the PDF tags tree.

This is different than in a Word to PDF conversion where the same scenario would result in one <table> tag for the table, regardless of how many pages it spans.

The accessibility guidance provided online only shows examples of tables that are contained within 1 page so I'm not sure how to address this issue for our scenario where the table spans multiple pages. 

NOTE: Originally I posted this at the following location - Table that spans multiple pages within a Paginated... - Microsoft Fabric Community - but am re-posting here in the "Issues" area of the community based on a comment. 

[Anonymous]

Hi @bethwhitmer ,

If I understand you correctly , there is a very large table in your report and it is not possible to display the whole table in a single page in a paginated report?

As far as I know, the best thing is that you can optimize the size of your table before doing so.

Best regards.
Community Support Team_Caitlyn

[bethwhitmer]

@Anonymous Yes, that's correct. Unfortunately, the table must span multiple report pages. We don't have an option to change this given the amount of data we need to display.