Hi,
When we create the pdf using aspose.words footnote tag is at the end of the tags in tag structure and it is also adding extra link tag. we have a requirement that we need to create footnote in such a way that footnote tag should be tagged right after the footnote link so that screen reader would read footnote in logical order. Is there anyway we can achieve this using aspose.words?NVDATest.zip (41.4 KB)
Please also ZIP and upload your input Word document here for testing.
Please also provide a comparison screenshot highlighting the problematic areas in Aspose.Words generated PDF file with respect to your expected output PDF and attach it here for our reference.
We will then investigate the issue on our end and provide you more information.
We have logged your requirement in our issue tracking system. Your ticket number is WORDSNET-17824. We will further look into the details of this requirement and will keep you updated on the status of the linked issue.
Upon further investigation, we have identified the following two separate issues:
- The extra link tag. This issue will be resolved as per WORDSNET-17824.
- Request to move footnote tags close to footnote link and not at the end of the page. The issue ID of this enhancement is WORDSNET-17885.
Also, here is the quote from specifications:
Both Aspose.Words current output and your requested output are correct according to specifications. So, we should consider this request not as a bug but as an enhancement/new feature. MS Word and Acrobat plug-in also save the footnote tags similar to Aspose.Words.
I am afraid, currently we do not have any plans to start work on the second issue i.e. WORDSNET-17885. However, we will keep you posted on any further updates on it and let you know when it will be implemented in future. We apologize for your inconvenience.
The issues you have found earlier (filed as WORDSNET-17824) have been fixed in this Aspose.Words for .NET 19.1 update and this Aspose.Words for Java 19.1 update.
It is to update you that the problem (WORDSNET-17885) actually requires us to implement a new feature in Aspose.Words API and we regret to share with you that the implementation of this issue has been postponed for now. There are no estimates available at the moment. However, the fix of this problem may definitely come onto the product roadmap in the future. You will be notified via this thread as soon as this issue/feature is resolved/supported. We apologize for any inconvenience.