[PDF/UA] Link Annotation not inside Link structure element

[Amin.Gan]

Hello,

Thanks for your following up.
Sorry, these two issues have not been resolved yet. Due to the complexity of the problems, our dev team is actively seeking corresponding solutions. At the same time, I will also urge them again. If there are any updates, I will notify you immediately. Thank you for your patience.

Sincerely,
Amin
E-iceblue support team

[berrydictu]

Hello,

As almost 9 months have passed, I am curious if you have an update on the possibilities to make link annotations inside link structure elements and on the support of artifacts in PDF documents.
In the near future, we will need to label our PDF as 'accessible', so we are really looking out for these features.

Kind regards,
Berry

[William.Zhang]

Hello,

Thansk for your following up.
Sorry, there is no breakthrough progress on these two issues yet. Our developers are still investigating solutions. If there is any good news in the future, I will inform you in time.

Sincerely,
William
E-iceblue support team

[berrydictu]

Hello,

Would it be possible to prioritize this a bit more? Additionally, could you provide more clarity on if and when we might expect a solution? No is an answer too, we just can't wait much longer. We are currently in the process of making some important decisions regarding how we will proceed in the future. That's why we are now exploring various alternative solutions to ensure we can produce a PDF file that is accessible enough within the standard we are obliged to follow.

I hope to hear from you soon.

Kind regards,
Berry de Groot

[William.Zhang]

Hello,

Thanks for your following up.
Regarding the "link annotation" issue, our development team is trying to add a new interface to enable annotation to be nested in link tag. We cannot estimate the completion time yet. But we will do our best to achieve it.
For the "Artifact" issue, our development feedback can be implemented through the following code snippet. After adding, it will be shown in the attached screenshot. Is the pdf you currently generate incorrect? To help us investigate further, can you take a screenshot to show us, or provide a pdf file you hope to achieve. Thanks in advance.

Code: Select all

 PdfStructureElement figure1 = article.AppendChildElement(PdfStandardStructTypes.Figure);
 //Set Alternate text
 figure1.Alt = "replacement text1";
 figure1.BeginMarkedContent(doc.Pages[0], null);
 PdfImage image = PdfImage.FromFile(@"E-iceblue.png");
 doc.Pages[0].Canvas.DrawImage(image, new PointF(40, 200), new SizeF(100, 100));
 figure1.EndMarkedContent(doc.Pages[0]);

 PdfStructureElement figure2 = article.AppendChildElement(PdfStandardStructTypes.Figure);
 //Set Alternate text
 figure2.Alt = "replacement text2";
 figure2.BeginMarkedContent(doc.Pages[0], null);
 doc.Pages[0].Canvas.DrawRectangle(PdfPens.Black, new Rectangle(300, 200, 100, 100));
 figure2.EndMarkedContent(doc.Pages[0]);


Sincerely,
William
E-iceblue support team

[berrydictu]

Hello,

Thank you for this update. We are trying to make this work. Tagging the element as an artifact by making the second parameter of the BeginMarkedContent method null does help: elements are marked as an artifact in that case.

However, when we do this, the content must still marked on an structure element (element.BeginMarkedContent(doc.Pages[0], null)). That means the artifact is still contained in the StructureTreeRoot (see attachment). For semantic elements like the figure you use in your example, this is probably correct. But there is a number of elements that has no meaning in the document, i.e. horizontal lines or gray blocks that visually enhance the document. These elements should not be contained in the StructureTreeRoot. They should only be an artifact, and nothing more than that.

The Pdf Accessibility Check tool (which I mentioned earlier) now shows errors that there are artifacts present inside tagged content and that there is tagged content inside artifacts. We should not encounter these errors.

What can be done to make sure that artifacts are tagged as an artifact, but do not show up in the document structure?

[William.Zhang]

Hello,

Thanks for your inquiry.
To help us investigate your issue more accurately, could you provide the latest code and generated documentation, and provide more details about your requirements? It would also be helpful if you could share the steps you took to achieve your requirements using other tools (e.g., Adobe Acrobat DC ). Thank you in advance.

Sincerely,
William
E-iceblue support team

[berrydictu]

I tried to build a very small example application to isolate what we do. It will generate a PDF file which you can open with the PAC tool and see what the result is. Mind you: when you click a structure element which contains a path element, the PAC tool will crash (probably because something is generated which is not compatible with the standards).
If you have any questions, please let me know.

[William.Zhang]

Hello,

Thanks for your reply.
I've attached a document. Could you please confirm whether this is what you're looking for? If so, I'm afraid we don't currently support this feature. If you do need it, I'll confirm with our development team whether it's feasible. I look forward to your reply.

Sincerely,
William
E-iceblue support team

[berrydictu]

Hi William,

This, unfortunately, is indeed what we are looking for.
I am curious now: is fully supporting the PDF standards, like PDF1.7, PDF/UA and PDF/A on your roadmap, and where are those milestones on the timeline? Do you have more information about the plans with the Spire.PDF product planning?

In the mean time, i'm afraid we are forced to have a look at other options, because the requested features are on a critical timeline for us.

[William.Zhang]

Hello,

Thank you for your confirmation. Currently, our Spire.PDF does not yet support creating documents in this format, and I have already forwarded your latest requirements to our development department. They will investigate as soon as possible to determine if it can be implemented. If there is any good news, I will notify you. Thanks for your understanding.

Sincerely,
William
E-iceblue support team