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

Free Support Forum - aspose.com

WCAG Accessibility Support in pdf documents

Hi Team,


We are using ASPOSE for Words to generate a pdf from a word template. Our application fills the word template with the appropriate data and generates a pdf… The resultant pdf document is failing accessibility checks by Acrobat Pro DC . The main failures are listed below
  • Tagged PDF (Document is tagged PDF)
  • Primary language (Text language is specified)
  • Title (Document title is showing in title bar)
  • Tagged content (All page content is tagged)
  • Tab order (Tab order is consistent with structure order)
  • Figures alternate text (Figures require alternate text)
  • Nested alternate text (Alternate text that will never be read)
  • Associated with content (Alternate text must be associated with some content)
  • Hides annotation (Alternate text should not hide annotation)
  • Other elements alternate text (Other elements that require alternate text)
  • Rows (TR must be a child of Table, THead, TBody, or TFoot)
  • TH and TD (TH and TD must be children of TR)
  • Headers (Tables should have headers)
  • Regularity (Tables must contain the same number of columns in each row and rows in each column)
  • List items (LI must be a child of L)
  • Lbl and LBody (Lbl and LBody must be children of LI)
  • Appropriate nesting (Appropriate nesting)
We are currently using the 14.2 version of Aspose For Words… Would be great if we can get the following information

  1. Does Aspose For Words support the generation of Accessible pdf documents and if so from which version.
  2. If generation of Accessible pdf documents is supported, are there any guidelines that we need to follow while creating our .doc template
Any help is appreciated.

Regards
Sabarish

Hi Sabarish,

Thanks for your inquiry. 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 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.

As soon as you get these pieces of information ready, we'll start investigation into your issue and provide you more information. Thanks for your cooperation.

PS: To attach these resources, please zip them and Click 'Reply' button that will bring you to the 'reply page' and there at the bottom you can include any attachments with that post by clicking the 'Add/Update' button.

Thanks for the quick reply… We will do that… In the mean time are there any standard guidelines that we should follow to ensure that the pdf document is accessible

Hi Sabarish,


Aspose.Words currently does not fully support the generation of Accessible PDF. But most of the issues could be fixed if you enable PdfSaveOptions.ExportDocumentStructure. Hope, this helps.

It would be great if you please attach sample document here for testing.

Best regards,

Hi Awaiz,


Thanks for the quick reply… The docuemnt is a confidential document. So we will not be able to send you the document .We tried generating the document with the following settings for PDFSaveOptions

PreserveFormFields = true,
ExportDocumentStructure = true,
Compliance = PdfCompliance.PdfA1a,

It solved a lot of issues… we are trying to work through the other issues. Mean while you had mentioned that the pdfs generated are not fully accessible… Cani you let us know the level of accessibility - PDF/A-1,PDF/A-2 or PDF/A-3

Regards
Sabarish


Hi Sabarish,

Thanks for your inquiry. Aspose.Words does not support PDF standards compliance level PDF/A-2 and PDF/A-3.

We have made this forum thread as private. Now only you and Aspose staff members can access this forum thread. Could you please attach your input Word document here for testing? We will investigate the issue on our side and provide you more information on this.

Hi Tahir,


Thanks for the support… For the time being , can you make this post public so that i can share the thread with my colleagues to indicate the current status.

Also would be a great help if you can guide me on how to make the title of the generated documents show up in title bar , when opened in Acrobat reader. Thats one of the remaining issues

Regards
Sabarish




Hi Sabarish,

Thanks for your inquiry. We need your sample document for further testing on our end.

It is safe to attach files in the forum. If you attach your document here, only you and Aspose staff members can download it. Also you can send the file to my e-mail as described here:
http://www.aspose.com/corporate/purchase/faqs/send-license-to-aspose-staff.aspx
Best regards,
Hi Sabarish,

Sabarish:
Also would be a great help if you can guide me on how to make the title of the generated documents show up in title bar , when opened in Acrobat reader. Thats one of the remaining issues

We have logged your requirement in our issue tracking system as WORDSNET-14190. Our product team will further look into the details of this problem and we will keep you updated on the status of this issue. We apologize for your inconvenience.

Best regards,

Hello ,


Regarding WORDSNET-14190 , the same problem is mentioned in the post given below

Setting DisplayDocTitle key on converting to PDF(Adobe Acrobat Accessiblity Compliance Check)

Do we need the license of Aspose.pdf to fix this issue

Regards
Sabarish

Hi Sabarish,


Thanks for your inquiry. Unfortunately, this issue is currently pending for analysis and is in the queue. We will be able to provide more information after when analysis of this issue is complete. Sorry for the inconvenience.

Best regards,

@ssathasivan,

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

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

A post was merged into an existing topic: Accesibility not avaliable in when converting from word to pdf