In your earlier reply, you mentioned there are two ways to include xmp meta data in prince pdf,
So, I thought the feature is available in prince. May I know both the options(above) are taking up in support request or 2 option is already available in current version? If so, how can I do it? Note: I'm talking about only xmp meta data not default properties like subject/keywords/title etc.
I saw that the first question about accessibility was placed in 2005, it's now 2017 and correct me if I'm wrong but Prince still don't generate an accessible PDF. As you know we have to deal with legislation and as a bank we can't afford that we exclude customers. So I ask the the same question again when can we expect a change in that direction? If we have to wait another 12 years we are forced to look for another solution. I'm looking forward to your reaction.
Is there some documentation on how to create a properly tagged PDF with PrinceXML? When I enable one of the above with the command line option --pdf-profile="PDF/A-1b" then open the resulting PDF in Adobe Acrobat Pro and do a "Full Check" regarding accessibility, it reports the document is not tagged.
If I understood correctly, you are expecting the "Royalty Statement" and "February 2020" headings to be tagged and show up in the reading order.
As those headings come from elements that have been removed from the normal flow and placed into page header regions, their contents will be marked as pagination Artifacts (i.e. not "real content") and won't show up in the reading order. This is normally desirable as you don't want screen readers to read out running headers, page numbers, and so on.
There is currently no way to tell Prince to treat the contents of header and footer page regions as real content, but we are considering it.