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.
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.
Hello. Are there any news about PDF accessibility support? When do you plan to implement it (a rough estimation)?
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.
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.
Aspose PDF 508 compliance
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 https://en.wikipedia.org/wiki/PDF/UA):
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:
Thanks for reviving this thread.
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.