If a table has “TextWrapping” set to “Around”, the table is placed last in the TaggedContent list when converting to PDF. The element are places visually correct, but gives an incorrect order when using a screen reader for accessibility.
@kim4848 Thank you for reporting the problem to us. For a sake of correction it has been logged as WORDSNET-24198. We will investigate the issue and let you know once we have more information for you or when the issue is resolved.
By the way, MS Word also has problem with proper tag order when floating content is used.
in.docx (12.7 KB)
ms.pdf (41.1 KB)
aw.pdf (19.3 KB)
@kim4848 Floating tables (and other floating content like shapes) could be located anywhere on the page. Unfortunately it is not possible to properly determine the correct position of floating table in logical structure in general case. For now Aspose.Words puts floating content at the end of the page logical structure. The only thing we can do here is to put the floating table at the place where it is located in the DOM (which may not be correct in some cases).
As a workaround for this issue you could try to use inline tables instead of floating. Or alternatively you could reorganize the logical structure on postprocessing of Aspose.Words PDF output.