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

Free Support Forum - aspose.com

Adobe Accessibility Check fails for Tables

Attached is SampleTemplate.pdf that is generated from SampleTemplate.rtf file using Aspose.Words for .NET library.

We are not able to resolve Adobe’s Accessibility check failure(Using Adobe Acrobat Pro DC) for tables that are used in sample documents.

There are 2 type of failures:
  1. Page Content -> Tagged content failure :
    This check always fails when we have a Table with repeating header on new page. The check always fails for the repeating header row on every new page.
  2. Tables -> Headers failure:
    This check always fails for tables.
Is there a way to resolve this failures using either Aspose.Pdf or Aspose.Words library? We currently have OEM license to Aspose.Words library but are planning to get additional OEM license for Aspose.Pdf if we are able to resolve these issues using pdf library.

Thanks.
Hi Samir,

Thanks for your inquiry. We are working over your query and will get back to you soon.

Best regards,

Thanks Awais for taking a look into this. We are eagerly waiting for a resolution.

Thanks.

Hi Samir,


Thanks for being patient. I tested the scenario and have managed to reproduce the same problem on my end. For the sake of correction, I have logged this problem in our issue tracking system as WORDSNET-12249. Our product team will further look into the details of this problem and we will keep you updated on the status of correction. We apologize for your inconvenience.

Best regards,

Thanks for the update Awais, few follow up questions:

1. Any approximate ETA when the bug fix will be available? Anyway to speed up the process(ie. buying Enhanced Support, etc.)?

2. Is this something that can be work-around from Aspose.Pdf library? ie. open up the pdf and then add the required tags/properties manually from Aspose.Pdf library.

Thanks.

Hi Samir,


Thanks for your inquiry.
Samir:
1. Any approximate ETA when the bug fix will be available? Anyway to speed up the process(ie. buying Enhanced Support, etc.)?
Regarding WORDSNET-12249, unfortunately at the moment we cannot provide you any reliable estimate as this issue is currently pending for analysis and is in the queue.

We understand that this issue is important to you; normally when an issue is reported by a customer via our regular product forums, it is added to the pool of current issues being worked on by our product teams. Our product teams 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. However, due to the nature of some bugs and the number of features we are working on, this doesn’t always mean we can fix every bug within a short time after it’s reported.

That being said, we fully understand that you are keen to get a fix to your particular issue, please have a look at enhanced support options - e.g. purchasing Priority Support will allow you to post your issues in our Priority Support forum and raise the priority of these issues directly with our development teams, if possible, we will then aim to get a resolution to your issue as soon as we can. Many Priority Support customers find that this leads to their issue being fixed in the next release of the software.

If you would like to take advantage of Enhanced Support then please request a quote in our purchase forum - http://www.aspose.com/community/forums/aspose.purchase/220/showforum.aspx

Samir:
2. Is this something that can be work-around from Aspose.Pdf library? ie. open up the pdf and then add the required tags/properties manually from Aspose.Pdf library.
We are checking this scenario and will get back to you soon.

Best regards,
samirjaiswal:
2. Is this something that can be work-around from Aspose.Pdf library? ie. open up the pdf and then add the required tags/properties manually from Aspose.Pdf library.
Hi Samir,

Thanks for your patience.

Currently I am afraid Aspose.Pdf for .NET does not support the feature to fix Accessibility check failure issues, but for the sake of implementation, I have logged it as PDFNEWNET-39226 in our issue tracking system. We will further look into the details of this requirement and will keep you updated on the status of correction. Please be patient and spare us little time. We are sorry for this inconvenience.

Can you please let us know status of WORDSNET-12249 and PDFNEWNET-39226 issue?

Hi Samir,

The issues are in analysis phase. We will be able to share more details once the issues have been analyzed and planned for a specific release. Sorry for the inconvenience.

Best Regards,

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


This message was posted using Notification2Forum from Downloads module by aspose.notifier.