Friday 18 October 2024
Work with me on accessible PDF projects – whether you handle design in‑house or through an agency.
If you’ve created printed reports, strategies or leaflets before, you’ll recognise most of the steps in creating an accessible PDF – brief, content, design and production. Producing accessible PDFs follows a similar path, but there are a few crucial differences that affect timings and budget. Understanding these upfront makes projects smoother and helps avoid last‑minute surprises.
Accessible PDFs differ in two key ways:
Accessible PDF standards include requirements that mean accessibility touches every phase of the project, from content creation and design to final testing.
To make your content accessible, you’ll need to consider things like hierarchical headings, meaningful link text, minimal use of acronyms and initialisms, and avoiding long runs of endnotes.
Design is accessible when there is, for example, a clear reading order, colour combinations that meet contrast requirements, a lightened cognitive load for the reader, suitable type sizes, and an InDesign file set up so the exported PDF can be remediated efficiently.
I can advise on content structure and design, or step in once you have a draft, depending on your team’s confidence and capacity.
For print‑only projects, designers rarely set up files with accessibility in mind, because there’s no need. For accessible PDFs, we need to allow time in our project schedule to prepare the InDesign file for accessibility.
This additional step includes setting a logical stacking and text flow order, configuring hyperlinks and mapping styles to export tags. The aim is to use InDesign’s built‑in capabilities as far as possible, so the exported PDF is in good shape and the later remediation phase is faster and more cost‑effective.
Even with accessible content, design and a well‑prepared InDesign file, it’s unusual to get a fully accessible PDF straight from export. Additional behind‑the‑scenes work is almost always needed to fix tagging omissions or errors introduced by the originating software. This work is called remediation – our second additional project phase.
Finally, testing checks whether the file behaves as expected for people using assistive technology. I test with Acrobat’s accessibility tools, PAC and the NVDA screen reader to confirm that the document can be navigated logically and that key information is announced correctly.
That means, in practice, the full project process looks like this:
Clients involve me at different stages. Some ask for guidance from the start; others bring me in once they have a design.
Wherever possible, I recommend involving me during the design phase. It almost always saves time and reduces frustration later.
If you’re looking for support with an accessible PDF project, you can learn more about how I work with clients on my Accessible PDF design, remediation & testing page.
If you’re planning a report, strategy, policy or other PDF and want to make sure it’s accessible, I’m happy to talk through your project and where accessibility fits, or review one existing PDF and outline the steps needed to bring it up to standard. Just send me a message!
Recent posts
Featured posts
Hello! I’m Sarah, an independent typographic designer, helping businesses to communicate their unique selling points through printed marketing and communications.
I’ve been sharing my knowledge about design, typography, marketing, branding and printing since 2014. I hope you enjoy reading my blog.

Sarah Cowan