I converted DOCX file (which is Accessibility compatible) to PDF document with the code mentioned in this link Does Aspose have Accessibility Support for Document Comparison File? - #4 by alexey.noskov, and I checked the resultant PDF document with Adobe’s “Check for Accessibility”, but it failed the Table > Regularity check (please check attached image_1 & image_2). Can we fix this issue with Aspose like using any other compliance method, or is this an expected outcome ?
@Kldv As it mentioned in the warning description, there are rows with different number of cells in the table, so the table is considered as irregular.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): WORDSNET-27834
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
@Kldv I have created an issue in our defect WORDSNET-27834 tracking system. We will keep you update and let you know once the problem is resolved or we have more information for you.
Thanks @alexey.noskov, We will be purchasing the Aspose.Words license. Once we have obtained the license, we will raise a ticket using the Paid Support services.
@Kldv We completed analyzing the issue and most likely the issue will be closed as Not a Bug or as Won't Fix.
It is perfectly OK to have a table with jagged rows having a different number of cells in a .docx document 27834s1.docx (15.8 KB) . The document has a very simple table where row 1 has two columns and row 2 has 1 column only.
On conversion to pdf via MS Word, this document fails table regularity check: 27834s1.ms.pdf (45.7 KB)
Similarly, the table in the original document has a different number of columns in the first row. If you unzip it and look at trPr element of the first row, you can see gridAfter element indicating that one column is missing.
So the same “table irregularity” is present in the source document, Aspose.Words conversion merely preserves it.
The issue can be worked around by splitting the table, grouping rows with the same number of columns into separate tables.
It will not actually improve readability in any way though. It can also result in a loss of some information in the logical structure or require some special handling. For example, if the table had header rows repeated on each page, after splitting the table the new tables must still be linked to the header (which is now in a separate table) somehow.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.