Hi,
Our client requested our pdf output to be web accessible.
They are referring to making PDF to be screen reader and assistive technology friendly for their customers.
Does anyone have information regarding this, or implementation or guidelines of how to go about it in Designer? (Thats Im assuming how we compose our document)
Thank you heaps in advanced.
Kind regards
E
Hello @edanting,
A good choice is to apply the Create Preview PDF task for this. The PDF preview generated by this task is typically used for previews embedded in webpages.
Please check this reply from back in 2019 for possible solutions for implementing the Create Preview PDF task.
Hi Marten,
The “web accessible” term might be a bit misleading (I have updated my post title). But our client coined it as “Web accessible”.
I dont think its about making the pdf be serve via http. But making the PDF screen reader friendly and making sure the elements are tagged. So assistive technologies can read its content.
I supposed its possible since Designer composition is based on HTML?
Hi
As a print unit at a university, accessibility issues with pdf often come our way, one tool we use to check and fix pdf is from
It really good, fixed a pdf for a blind student the other day and she reported that it was pretty much perfect when we had applied the recommendations from the tool above.
I have not yet run any pdf output from PlanetPress though the PAC checker yet, but I will give it a go later and report back
Hope that helps
Ollie
Hi @Ollie
Thank you for your insight and recommendation 
Much appreciated.
Ernani
Considering the European Accessibility Act, it’d be really interesting to get some info on this.
FYI. We’re planning to release a Public Beta of the new version of OL Connect on June 23rd, which will include PDF/UA output. It generates the logical structure tree, apply alternate text for images, set the document language and title, embedded fonts etc. It’s a significant step towards generating accessible PDF output.
Please note that PDF/UA output alone doesn’t guarantee proper accessibility. Template designers must ensure logical reading order, proper tagging of content (such as headings), adequate color contrast, and the conversion of essential image-based information into selectable text (for example, don’t lock important information, like bank details, in a background image).
