We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Accessibility Issues are Appeared after DOCX to PDF conversion using .NET

Hi ,

We are using aspose version 19.12.0 and its below versions. While we are converting word to pdf, we are getting accessibility issues. We have a valid license of aspose.word till 30th july 2020.

Can you please help us to fix this.

@sapnajain5

To ensure a timely and accurate response, 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 share the screenshots of accessibility issues that you are facing.

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.

Hi,

I am generating PDF file from a word document using Aspose.word 19.7.0 version.

But in generated PDF, I am getting accessibility issues.

  1. Below is the input word file : -
    BaseNonQC_EN_Template.zip (1.2 MB)

  2. Below is the out PDF file, in which I am getting accessibility issues.
    ContinYouGOLDEN_Policy_Joey Tribiani_March_31_2021 (15).pdf (858.6 KB)

  3. Below is the attached screen shot of accessibility issues:-
    AccessibilityErrorsScreenShot.PNG.jpg (333.8 KB)

  4. Below is the desired output PDF. In this pdf I am getting very less accessibility errors.
    DesiredOutPDF.pdf (1.0 MB)

Please let me know if you need any other information.

@sapnajain5

We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-22083. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

Hi,

Any update on this issue. Please let me know.

Thanks

@sapnajain5

We try our best to deal with every customer request in a timely fashion, we unfortunately cannot guarantee a delivery date to every customer issue. We work on issues on a first come, first served basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers.

Currently, your issue is pending for analysis and is in the queue. Once we complete the analysis of your issue, we will then be able to provide you an estimate.

@sapnajain5

Your issues are related to invalid input document and to incorrect using of PdfSaveOptions:

  1. Alternate text: the issue is caused by the images/shapes that does not have the alt text. To fix it, you can open the document in MS Word and check for Accessibility. validation.jpg (251.7 KB)
  2. All content should have the alt text or be marked as decorative (support for this feature will be added in the May release Aspose.Words 21.5).
  3. Pdf logic structure: to export the logical structure of the document needs to use a PdfSaveOptions:
PdfSaveOptions so = new PdfSaveOptions(); 
Document doc = new Document(path); 
so.OutlineOptions.HeadingsOutlineLevels = 5; 
so.DisplayDocTitle = true; 
so.ExportDocumentStructure = true; 
doc.Save(outPath, so);
  1. The issue with invalid table headers is already known and was logged with issue ID WORDSNET-21795. It is a missing feature in Aspose.Words. We will inform you via this forum thread once this feature is available.

A post was split to a new topic: Support of decorative shapes for document accessibility

The issues you have found earlier (filed as WORDSNET-22083) have been fixed in this Aspose.Words for .NET 21.7 update and this Aspose.Words for Java 21.7 update.