We 're using Aspose.words 17.9.0 version and in our case we are using layout tables to generate tables with nested data. We’re using PDFSaveOptions to save as PDF file. Right now we’re facing problem where Layout tables are failing to comply with ADA and exact problem is table inside table (nested tables) where ‘th’ is not getting recognized in this scenario. We are in need of layout tables to be continued to use and at the same time Is there a way where we can flag the table in such a way that automated scans and screen readers aren’t expecting a “real” table.
So that it will help us to skip the accessibility issues for the layout tables. Or else please let us know if any possible solution from Aspose which may help us to clear through ADA accessibility issues.
If you still face problem, please attach the following resources here for testing:
Your input Word document.
Please attach the output PDF file that shows the undesired behavior.
Please attach the expected output PDF file that shows the desired behavior.
Please create a standalone console application (source code without compilation errors) that helps us to reproduce your problem on our end and attach it here for testing.
Please share the steps that you are using to check ADA accessibility issues.
As soon as you get these pieces of information ready, we will start investigation into your issue and provide you more information. Thanks for your cooperation.
PS: To attach these resources, please zip and upload them.
@tahir.manzoor Sure, thank you. Will share the resources which you’ve asked.
Meanwhile a quick question on upgrading to latest Aspose version. Would it require more work from development perspective for upgrading Aspose.words to latest version. Basically I would like to know, from Code per se whether the latest version will it be backward compatible or not.
There is no backward compatibility. Please check the release notes of Aspose.Words for .NET from here:
You can create simple new .NET application that converts document to PDF using PDFSaveOptions and test your case. If you face the same issue, please share the requested resources here for testing. We will then investigate the issue and provide you more information on it.
Thanks for your reply. We noticed in Aspose.words documentation, the heading rows won’t work inside nested tables, this is the same problem we facing with ADA compliance right now where it expects header in any tables. Though we can understand from the documentation that this is the limitation of Microsoft Word itself, by any chance if there is any alternate solution for this scenario and if you can share that. That would be much helpful.
Please note that Aspose.Words mimics the behavior of MS Word. In this case, you need to add heading row explicitly on each page of document. You can use layout APIs to find the page number of a node e.g. Row and insert the desired row or nested table at desired page. Hope this helps you.