Can you share the steps by which do you want to create a PDF/UA file?
Acrobat already has an option to fix tagging issues in the PDF to make it PDF/UA compliant using Tools > Preflight.
The problem is not 'broken tags' it's 'no tags at all'.
Adobe PDF Print simply does not generate PDF/UA files from the browser. (Browser may be failing to generate an accessibility tree, which is not Adobe's fault, but reflects badly on PDF as an accessible and portable format)
Semantics are entirely lost when you create a PDF using the Adobe PDF print gadget.
The use case is:
Make (or visit) a WCAG compliant HTML5 page in any browser that supports Adobe PDF print.
Print the page to PDF using Adobe PDF print.
Expected Result - Semantics converted to corresponding PDF/UA tags in output
Actual Result - Non-tagged PDF is output
Can you please on “does not seem to ‘see’ or announce any of the tags.” .
I checked the pdf, the order of reading the document is the same as in the tags panel. It reads in the same order. Also it announces tag type like headings, links, table, graphic etc.
Please elaborate about what exactly is needed here with appropriate examples.
Sure, you could try any of the PDF/UA files from pdfa.org, such as this one (tested with PAC3 and passes all PDF/UA requirements, tested also with Acrobat Pro DC for Windows Accessibility Full Check, passing all but manual checks). VoiceOver reads the text, but does not seem to 'see' or announce any of the tags.
Mac System is 10.15.1
Mac Acrobat Reader DC Continuous Release Version 2019.021.20061
We are always working to make it a better of experience for our accessibility customers.
We’ll be adding the support of Undo/Redo in order panels and Reading Order Tool in our coming releases.
Can you please tell me why you need the Tags Panel and Reading Order to be merged.
"We are always working to make it a better of experience for our accessibility customers"
Does that include the Mac version? I can't get any PDF viewer on Mac to play properly with VoiceOver, expecially including Acrobat Reader.
As long as this goes unfixed, Adobe are choosing to make PDF unviable in various jurisdictions, including USA, Canada, EU, UK and others, because accessibility compliance is now mandatory in these regions, for the public sector at least, and there is legislation for the private sector on the road map too. Laws have already passed about accessible digital content in France for larger firms. Wake up Adobe!
I’m able to read the document in the same order as the tags. Can you specifically tell me which part of the document is not following the order.
How are you viewing the file? PDF viewers for Browsers and Acrobat on Mac do not expose any accessibility tree.
I downloaded it and opened it in Acrobat on Windows, and the reading order looked fine (for a RTL language like hebrew, at least), and the accessibility Full Check had only 2 minor issues calling for manual checks..
However, Acrobat complained about missing tags when I started up NVDA, which I find odd. The tags are definitely there.