The product team has already been intimated and they are currently investigating this problem. However currently we cannot share the possible timelines but as soon as we have some definite updates, we will let you know.
The product team has started investigating the earlier requested feature but in order for us to implement it in appropriate manner, we request you to please share detailed specifications, so that we can implement accordingly.
Per your request for detailed specifications, please see below:
In order to be 508 compliant, all PDF documents must contain well-formed accessible tags.
When a PDF is processed using Aspose, all tags which existed in the template PDF are not recreated and or removed from the destination file. This means, when our application processes a PDF, all the tags are removed. In order for our application to be 508 compliant, Aspose must make sure the Tags in the original PDF template are recreated in the, Aspose Processed, PDF file.
Four files are attached for additional detail:
Aspose code.txt – This file contains the PDFEngine code where our application’s code interfaces with the APO objects.
Template.pdf – This is the source PDF our application uses as the template. This file contains tags.
Processed by Aspose.pdf – This is the file generated by Aspose. You will notice that all the tags from the Template.pdf file have not been created.
Manually Created.pdf – This file is a copy of the template.pdf file. You can see that when the form is manually completed and saved, Adobe did not remove the existing tags.
We need Aspose to do the following:
1) When Aspose processes a PDF template, they need to recreate any tags, from the original template, in the output file.
2) These tags must maintain the same format, structure and content as they exist in the template file.
Please let me know if clarification is required for any of this information. Thank you.
Thanks for sharing the detailed specifications. We have passed on to the product team for proceedings and sure we will request you if we need any further details in this regard.
I’m seeking a status update on the development of the solution. The original estimate provided to us indicated this would be resolved between May 1st and June 1st. I would like to confirm if the product team is on track to deliver the solution within this timeframe.
Thanks for your inquriy. The investigation of the issue is still not completed. However we have again requested our product team to share the update status of the issue, we will update you as soon as we get a feedback.
Thanks for your patience. Our product team is analyzing your shared source document and code. However we will appreciate it if you please share a sample test solution, it will help us to address your issue more accurately and quickly.
I need confirmation of what you mean by “sample test solution”. We cannot share our code so I’m trying to understand if you are asking for something else.
Thanks for your inquriy. Yes, we meant by sample text solution an executable code to test your shared scenario, as we tried to understand your code but some references are missing e.g acme.Lib. You may share your sample solution via email, we do honor the customer information privacy.
We have attached a zip file containing a console application to assist in the development of the fix for this defect.
Embedded into the package is a pdf file that has fields and tags. If you open the original pdf file located in the bin\debug folder you can see the tag structure. Once you run the application, a new file will be generated using the ASPOSE API. The console application will give you the path to said file but you can locate it in the bin directory of the application.
When you open this newly created file, you will see that the Tag structure is not carried over into the new file.
Please let me know if this meets your needs. The solution of this defect is a critical need for our organization.
Since it has been nearly one month since the sample project was provided, I am seeking an update on the progress towards resolution. I would appreciate whatever information you can provide and an estimated resolution timeframe.
The product team is still investigating earlier reported issue and I am afraid its not yet resolved. However your concerns have been recorded with product team and as soon as we have some further updates, we will let you know.
Thanks for your interest in the feature. Our product team is working hard to implement subjected feature but I am afraid it is difficult to share any ETA at the moment. However, we have recorded your concern and will notify you ETA/update, as soon as it becomes available.
Our product team has further investigated the requested feature. In order to provide you a ETA, we need more detailed list of user
requirements. WCAG standard describes requirements to web contents to make it
accessible for peoples with disabilities. WCAG standard
requirements are quite broad and not always formalized, sometimes they
are rather recommendations than precise requirements and it is not clear how these requirements should be applied to Aspose.Pdf tools.
mikefisherow:
When you open this newly created file, you will see that the Tag structure is not carried over into the new file.
In reference to the information you shared in your issue description, you noticed that tags in source PDF
document are absent in your concatenated resultant document. Is this only problem which you met to accomplish your requirement or has set of the issues which should also be resolved? In other words we need list of requirements
which should be satisfied in order to plan this work and reasonably estimate
time required to resolve this issue.
The product team has further look into earlier request feature and in order to generate WCAG 2.0 compliant output, please try using PdfFileEditor.CopyLogicalStructure option as it saves tags in resultant document.
In case anyone is looking, it seems they just released a few updated versions that have new features releated to PDF/UA accesibility (PDF/UA is part of the new 508 standard, see PDF/UA - Wikipedia):
I’ve not yet tried it out, but here’s the forum post that alerted me to this, which includes some code examples in the most recent response from asad:
Your comments will definitely help grabbing attention of others who are interested in this new feature. We would like to add that we are working over adding more of the functionality related to 508 Compliance and we welcome suggestions and requirements from our customers in this regard which would definitely help us implementing the feature efficiently.
mikefisherow:
When you open this newly created file, you will see that the Tag structure is not carried over into the new file.