In this article, you will discover:

• Polished-looking PDFs are not always accessible.
• Good accessibility depends on structure and tagging, not appearance alone.
• Automated tools have their place, but human testing is essential to good accessibility.
• Accessible PDFs need to be planned from the beginning.
• Knowledge, testing, and time are critical to success.

Did you know it is possible for a PDF to look perfect and still be inaccessible?

That will likely come as a surprise to you.

After all, if a document is clearly laid out, professionally designed and easy to read, surely everyone can use it?

Unfortunately, that is not always the case.

With the introduction of legislation like the European Accessibility Act, and planned changes to the Web Content Accessibility Guidelines (WCAG), organisations are increasingly investing significant effort in making their websites accessible.

However, the documents they publish online still receive far less attention than they deserve.

Policies, reports, brochures and forms are uploaded every day, going on the assumption that a PDF is just a finished version of a document, but sadly, accessibility does not automatically come along for the ride.

Why so many inaccessible PDFs?

One of the greatest challenges around creating PDF documents is awareness: people don’t know that PDFs need to be accessible in the first place.

Digital accessibility is more often associated with websites and apps, while downloadable documents are somehow seen as separate from the digital experience.

Then, there is a common misconception that all PDFs are created equal.

In actual fact, two files can appear to be identical on screen but provide completely contrasting experiences for people using assistive technologies.

One might, for example, be designed with a clearly structured cascading heading hierarchy, effective alternative text and a logical reading order.

The other may contain none of these things.

To a sighted reader, there is no obvious difference.

To a screen reader user, important messages and meaning can be utterly lost.

That is why designers creating accessible PDFs must pay careful attention to reading order from the start.

Accessibility as a fundamental skill

Creating accessible PDFs takes knowledge that many professionals never learn when studying their craft.

Designers, marketers, administrators and communications teams create documents every day, yet accessibility training is also limited or entirely absent from workflows.

Another knowledge gap stems from many accessibility features being hidden away within advanced menus and export settings.

So it stands to reason that someone who does not know they exist will be unlikely to discover them by accident.

Finally, the increasing prevalence of easy-to-use design platforms has added yet more complexity to the situation.

More people than ever can create attractive documents, undoubtedly a positive development; however, these tools often prioritise aesthetic appearance over document structure, making accessibility harder to achieve from the get-go.

What we learned through manual accessibility testing

The scale of these challenges has become particularly clear during a recent project where a colleague and I have been creating and testing accessible PDFs for a client.

The process has been a learning curve for both of us.

My colleague comes from a design background and has been focused on creating well-structured, inclusive, but visually appealing documents.

My role has involved testing those documents using the JAWS screen reader.

Throughout the project, we identified a couple of issues that simply weren’t visible from a design perspective.

The document gave no clues to potential accessibility barriers on screen, but the experience of navigating it with a screen reader said otherwise.

One of the most interesting discoveries was that accessibility testing is rarely straightforward.

Different screen readers can behave in different ways.

In some cases, one screen reader would announce an image description exactly as intended, while another would ignore it completely.

That reinforced an important lesson: accessibility is not just about making a document technically compliant.

It is about understanding how real people will experience it using different technologies and different ways of interacting with content.

Why automated testing is never enough

Many organisations rely heavily on accessibility checkers, and these tools certainly have their place; quickly identifying missing document titles, tagging issues and other common technical fails.

The problems lie in automated tools’ inability to understand context, or replicate the steps of an authentic user journey.

A checker cannot determine whether alternative text actually conveys meaning, know if a table makes sense when it is read aloud, or tell you whether a user will understand the structure of a document when navigating by headings.

Accessibility is ultimately about usability, and usability requires human judgement.

Read our article ‘Technical expertise built on lived experience: Why our testers notice what others miss’ to learn more about how this philosophy shapes Passion4Social’s accessibility auditing and consultancy services.

The missing ingredients: Planning and time

Another common misconception and incidentally, the one that we dread most, is that accessibility can be added at the end of a project.

The authentically accessible PDFs are built with an inclusive design mindset from the start.

We cannot emphasise enough how document structure, heading levels, reading order, alternative text and navigation need to be considered throughout the design and content creation processes.

Attempting to address accessibility just before publication only creates unnecessary work and leads to issues being missed.

Organisations also need to recognise that accessibility takes time. Thorough testing, revisions and approvals cannot possibly be squeezed into the final few hours before a deadline.

Looking beyond the “Save as PDF” button

The reason we still encounter so many inaccessible PDFs rarely results from a lack of good intentions.

More often, it is the result of limited awareness, insufficient training, competing priorities and a belief that technology will solve the problem automatically.

Creating accessible PDFs requires knowledge, planning, testing and time.

None of those elements can be added with a single click; neither can they be left out of the process.

So, the next time you prepare a document for publication, ask yourself this: does this PDF merely look accessible, or can everyone actually use it?

If the answer does not immediately come to you, or you want to learn more about creating accessible PDFs, get in touch with us today.

We are here to support your every step, ensuring your downloadable documents are just as inclusive and easy to read as your website.

You can learn more about making everyday digital documents more accessible and inclusive for everyone by watching our webinar, ‘Create, Test, Include – Accessible Documents’.