Making the PDFs on your website accessible: a checklist
Short answer: Most PDF accessibility problems start in the source document. Build the document with real headings, lists and alt text in Word, PowerPoint, LibreOffice or your design tool, run its accessibility checker, then export as a tagged PDF rather than "printing" to PDF. Check the result with a screen reader or a PDF checker. And ask whether the content should be a web page instead: menus, price lists and opening times usually work better as HTML.
Restaurants publish menus as PDFs, estate agents publish brochures, service businesses publish price lists and forms. Many of these are scanned images or exported in ways that leave screen reader users with nothing to read, and they're awkward on phones for everyone. This checklist covers getting PDFs right, and deciding when not to use them.
1. First, should this be a PDF at all?
- ☐ Is it something people read on your site (menu, prices, services, opening hours)? A web page is usually better: it adapts to phone screens, is easier to update, can be found in search, and works with assistive technology without extra effort.
- ☐ Is it something people download, print or keep (a brochure, a detailed guide, a form for signing)? A PDF can make sense, ideally alongside an HTML summary.
- ☐ Is it a scan? A scanned image of a document is just a picture. Recreate it from the source, or at least run text recognition and then fix the result.
2. Build an accessible source document
Microsoft's guidance on accessible PDFs says the fastest way to make sure a PDF is accessible is to run the Accessibility Checker before generating it; once issues are fixed, Microsoft 365 uses that information to create accessibility tags in the PDF. Whatever tool you use, the source needs:
- ☐ Real headings using the Heading styles, not just bigger bold text.
- ☐ Real lists using the list tools, not typed dashes.
- ☐ Alt text on meaningful images, and decorative images marked as decorative.
- ☐ Simple tables with a header row defined, no merged cells where avoidable, and no tables used purely for layout.
- ☐ Descriptive link text ("See our delivery area map", not "click here").
- ☐ Document title set in the file properties, and the document language set.
- ☐ Sufficient colour contrast and no information conveyed by colour alone.
- ☐ Text as text, not text embedded inside images (common in designed menus and brochures).
3. Export a tagged PDF
Tags are the hidden structure that tells assistive technology what's a heading, a paragraph, a list or an image. Microsoft explains that tags let screen reader users read and navigate a document with tables of contents, links, bookmarks and alt text, and help content display on other devices.
- ☐ Microsoft 365 on Windows: use File → Save As (or Save a Copy), choose PDF, open Options, and make sure "Document structure tags for accessibility" is ticked, per Microsoft's instructions.
- ☐ Microsoft 365 on Mac: Microsoft describes choosing "Best for electronic distribution and accessibility" when saving as PDF, which ensures the PDF is tagged. It notes this option uses a Microsoft online service.
- ☐ LibreOffice: its PDF export options include Universal Accessibility (PDF/UA), which creates a file following the PDF/UA (ISO 14289) requirements; tagged PDF is automatically enabled when PDF/UA is selected.
- ☐ Design tools (such as desktop publishing apps): look for tagged PDF or accessibility export options, and set reading order and alt text in the source before export.
- ☐ Avoid "Print to PDF". It usually produces an untagged file.
4. Check the result
- ☐ Run a PDF accessibility checker in your PDF editor if you have one.
- ☐ Open the PDF with a screen reader (VoiceOver on Mac, NVDA on Windows) and check: are headings announced? Can you jump between them? Is the reading order logical, especially in multi-column layouts? Are images described?
- ☐ Try selecting and copying text. If you can't, it's probably an image.
- ☐ Zoom to 200% and view on a phone. Is it still usable?
- ☐ Check form fields (if it's a fillable form): each field labelled, tab order sensible.
5. Publish it properly on your site
- ☐ Link text says what the file is and its format: "Spring menu (PDF, 2 pages)".
- ☐ Provide the key information in HTML too: for example the menu items and prices on the page, with the PDF as a printable version.
- ☐ Use a sensible file name:
spring-menu-2026.pdf, notFinal_v7_USE_THIS.pdf. - ☐ Keep file size reasonable for mobile downloads: compress images in the source.
- ☐ Remove outdated PDFs, or replace them at the same URL so old links keep working.
A quick example (hypothetical)
A Brighton café posts its menu as a PDF exported from a design app: the dishes are part of a single background image, so a screen reader announces nothing and the text can't be zoomed cleanly. The café moves the menu text onto an HTML page with dishes, prices and allergen notes, and keeps a tagged PDF, rebuilt from a template with real headings and text, as the printable version linked from that page. Updating prices now means editing the page and regenerating one file.
6. Make it part of the routine
- ☐ Create an accessible template for recurring documents (menus, price lists, newsletters).
- ☐ Give the person who makes them a five-minute checklist (headings, alt text, checker, tagged export).
- ☐ Re-check whenever the template or the tool changes.
Check the accessibility rules that apply to your organisation; this checklist focuses on the practical steps.
FAQ
Can I fix an inaccessible PDF without the source?
Sometimes, with a dedicated PDF editor, but it's slow and fiddly. Recreating from the source, or publishing the content as HTML, is usually faster.
Is a PDF menu bad for SEO?
Search engines can read text-based PDFs, but a menu as an HTML page is easier to find, faster on phones and simpler to update.
What is PDF/UA?
A standard for universally accessible PDFs. LibreOffice, for example, can export to it directly.
Do designed brochures have to look plain to be accessible?
No. Good design and accessibility work together, as long as text stays real text, contrast is sufficient and the structure is tagged.
If your site relies on PDFs that nobody can read on a phone or with a screen reader, send us the ones that matter most and we'll suggest which to fix and which to turn into pages.