Many business websites are full of PDFs. Restaurant menus, price lists, brochures, application forms, annual reports, policy documents, event programmes, school circulars. They’re convenient to produce: someone designs a document, exports it and uploads it to the media library. But for many visitors, especially those using screen readers, magnification or mobile phones, these documents are difficult or impossible to use. Accessible PDFs, or better still web pages, solve that.
Accessibility laws and standards apply to documents published on websites just as they apply to web pages. More practically, a menu that a blind customer can’t read, or a form that a person with motor disabilities can’t fill in, loses you customers and creates frustration. This article explains when to avoid PDFs, how to create accessible PDFs when you need them, how to check them and how to present documents well on a WordPress site.
Why PDFs are often inaccessible
A PDF can be perfectly accessible, but most aren’t, for a few reasons:
- Scanned documents are just images of text. Screen readers can’t read them at all.
- Untagged PDFs lack the structural information, such as headings, lists, tables and reading order, that assistive technology needs. Screen readers may read them as one long block of text, or in the wrong order.
- Images without alternative text are invisible to screen reader users.
- Tables without header information become confusing strings of numbers.
- Forms without proper fields can’t be filled in electronically.
- Poor contrast and tiny text make documents hard to read for many people.
- Multi-column layouts often read in the wrong order.
On mobile phones, even accessible PDFs are awkward: they need zooming and scrolling, and they open in separate viewers.
First question: does this need to be a PDF?
The most accessible document is often a web page. For many common PDF uses, an HTML page is better for everyone:
- Menus and price lists work better as web pages. They’re easier to read on phones, easier to update and can appear in search results.
- Policies and terms belong on web pages.
- Event information and programmes are better as pages with clear headings.
- Simple forms should be web forms, which are easier to complete, validate and receive.
- Blog-style content and articles should never be PDF-only.
PDFs remain appropriate for documents that need to be printed in a fixed layout, legally formal documents, detailed reports where a downloadable version is expected and documents distributed beyond your website.
A good compromise is to publish the content as a web page and offer the PDF as an optional download for printing.
Creating accessible PDFs
If a PDF is needed, accessibility is far easier to build in at the source than to fix afterwards.
From Microsoft Word
Word can produce well-structured, tagged PDFs if the document is created properly:
- Use built-in heading styles, Heading 1, Heading 2 and so on, rather than making text bold and larger.
- Use real bulleted and numbered lists.
- Add alternative text to images and mark decorative images as decorative.
- Create tables with the table tool, mark the header row and avoid merged cells where possible.
- Use descriptive link text instead of pasted URLs.
- Set the document title and language in the file properties.
- Run Word’s built-in Accessibility Checker, under the Review tab, and fix issues.
- Export with Save As or Export to PDF, making sure the option to create document structure tags for accessibility is enabled.
From Google Docs
Google Docs can export PDFs, and recent versions include basic tagging, but results vary. For important documents, check the output carefully or export to Word first and create the PDF from there.
From Adobe InDesign
Professional brochures and reports are often designed in InDesign. Accessibility requires setting up paragraph styles mapped to export tags, ordering content in the Articles panel to control reading order, adding alt text to images, and exporting with tagging enabled. It’s very achievable but needs to be part of the designer’s workflow, so mention it when commissioning the design.
From Canva and similar tools
Online design tools produce attractive documents but often limited accessibility. If you use them for important documents, also publish the content as an accessible web page.
Fixing existing PDFs
Adobe Acrobat Pro includes tools to add and fix tags, set reading order, add alt text and run an accessibility check. Fixing complex documents can be time-consuming, so prioritise:
- Documents essential to using your services, such as forms, application guides and price lists
- Documents with high download numbers
- Documents required by regulation
For scanned documents, run optical character recognition first, then add structure, or better, recreate the document from the original source.
For documents that are rarely used and outdated, consider removing them.
Checking accessibility
Several tools help:
- Adobe Acrobat Pro’s accessibility checker
- PAC, the free PDF Accessibility Checker, which tests against the PDF/UA standard
- Screen readers, such as NVDA with a PDF reader, to hear how the document actually reads
Automated checks catch structural problems but can’t judge whether alt text makes sense or the reading order is logical. A quick listen with a screen reader is very revealing.
Presenting documents on WordPress
How you link documents matters too:
- Use descriptive link text that names the document and indicates the format and size, such as “Download the 2026 course prospectus (PDF, 2.4 MB)”. Avoid “Click here” or bare file names.
- Tell people it’s a PDF before they click, so mobile users aren’t surprised by a download.
- Give files meaningful names before uploading, such as course-prospectus-2026.pdf rather than final-v3-new.pdf. WordPress uses the file name in URLs and the media library.
- Add a summary on the page, so visitors know what the document contains without opening it.
- Offer alternatives, such as an HTML version or contact details for requesting the information in another format.
The File block in WordPress creates a download link with the file name and optional button. Edit its text to be descriptive. For multiple documents, a simple list with titles, descriptions, formats and sizes works well.
Keep documents current
Outdated PDFs are a common problem. Old price lists and expired forms remain in the media library and in search results for years. When you update a document, replace the file rather than uploading a new one with a different name, or redirect the old URL, so links and search results point to the current version. Media replacement plugins help with this.
Review your documents periodically and remove ones that are no longer valid.
A short checklist
- Could this be a web page instead? If so, make it one.
- If a PDF is needed, create it from a well-structured source with headings, lists, alt text and proper tables.
- Export with tags enabled, and set the title and language.
- Check with an accessibility checker and, ideally, a screen reader.
- Link with descriptive text, including format and size.
- Offer an alternative format on request.
Accessible PDFs take a little more care than inaccessible ones, but most of the work is simply using document tools properly. Once it’s part of the routine, it costs very little.
A worked example
A school published its circulars, fee schedules, admission forms and term calendars as scanned PDFs, many of them photographed on a phone. Parents using screen readers couldn’t read any of them, and most parents on phones found them awkward to zoom through.
The school changed its approach. Circulars became short posts in a dedicated category, readable on any device and searchable on the site. The fee schedule became an HTML table with a clear heading structure. The admission form became a web form with proper labels and validation, with a printable, accessible PDF offered for families who preferred paper. The term calendar became a page with a list of dates. Within a term, the school office reported fewer phone calls asking for information that was “in the PDF”, and parents commented that the information was much easier to find on their phones.
Frequently asked questions
Do accessibility laws apply to PDFs?
Generally yes. Standards like WCAG apply to web content, including documents. Laws such as the European Accessibility Act and India’s accessibility guidelines for government and many public-facing services reference these standards.
Is a scanned PDF ever acceptable?
Only with OCR and proper tagging, and even then the quality varies. Recreating the document from its source is better.
Can I just provide a Word document instead?
Word documents can be accessible, but they require software to open and display inconsistently on phones. A web page is usually the better alternative.
How do I know if my PDF is tagged?
In Adobe Acrobat Reader, open Document Properties and look for “Tagged PDF: Yes”. Tagging alone doesn’t guarantee accessibility, but its absence almost guarantees problems.




