We are using Aspose 17.10.x and the generated PDF should be 508 compliant. To be precise, when I view the PDF using Acrobat Pro DC/Reader and use “Accessibility” check feature of PDF, it should not list error like “Tageed Content - Failed” , “Tab order - Failed”, “Tagged form fields - Failed”,“Fields description failed” etc.
There is no source PDF, generated all the content dynamically and I cannot share the complete details of source code. But below is the sample which drives most of the logic. For your testing you can run below code in loop to generate X elements.
Document pdfDocument= new Document();
TextBoxField lblField = new TextBoxField(pdfDocument, new Rectangle(0, 0, 0, 0));
There is no way to create 508 compliant PDF. We have logged a feature request to create and edit accessible PDF files under the ticket ID PDFNET-26512 in our bug tracking system. We have linked your post to this ticket and will keep you informed regarding any available updates.
Kindly elaborate a bit more about the requirement like which type of the elements you need to extract from the PDF document. Please Zip your source PDF and accessibility report, and then upload to your reply post.
repeat above cells for 5 rows. When I use Acrobat DC Pro View -> Read Out Loud -> Read this Page Only. I expect it should read from left -> right like zipcodes, patients, 123. But its not happening even after setting Taborder(shared code above). In other words, it should read content of Row1 first then Row2…so on.
I hope I’m clear enough for you to comeup with test code. Let me know if it is doable, and if you can share your code that will be helpful.
We have tested your scenario with the latest version 17.11 of Aspose.Pdf for .NET API and reading feature of Acrobat table content from top left to bottom right. This is the output PDF: document_with_table_out.pdf (2.1 KB). Please try this output PDF, and then let us know how that goes into your environment.
We could not add a text box field in the table cell. We have already logged an investigation under the ticket ID PDFNET-43699 in our issue tracking system. We have linked your post to this ticket and will keep you informed regarding any available updates. However, if you can add a text box field in the table cell, then please share the complete code and Aspose.Pdf for .NET API version.
The linked ticket IDs PDFNET-26512 and PDFNET-43699 are pending for the analysis and not resolved yet. Our product team will investigate as per their development plans. We will let you know once a significant progress has been made in this regard.
This appears to be a request going back at least until 2011 (PDFKITNET-25060 - Convert PDF file to a 508 compliant PDF, PDFKITNET-25059 - Check whether the PDF file is 508 compliant, PDFNET-26512, PDFNEWNET-25060).
Is there an available roadmap as to when these features are expected to be complete? We have a number of clients asking to generate 508 compliant PDF’s.
We are getting details of the recent status, and will let you know soon in this thread. Besides this, we recommend our clients to post their critical issues (or ticket IDs) in the paid support forum. Please refer to this helping link: Aspose support options