Why convert PDFs to HTML instead of fixing each one

The usual answer to an inaccessible PDF is remediation: open the file, add tags, fix the reading order, write alt text, save, test, repeat. For one document that is reasonable. For a library of thousands it is slow, costly and never finished, because new files keep arriving.

What the guidance says

The UK government’s official guidance on publishing accessible documents says it is simpler to create HTML from a document than to try to make a PDF accessible for all users. Its advice is to publish content as web pages where you can, and to offer a PDF only when people need one. Read it at gov.uk.

Why HTML works better

• It adapts. Text reflows, resizes and works with screen readers, magnifiers and voice control on any device.
• It is easier to keep right. Structure is part of the format, so headings, lists and tables are marked up by default.
• People can find it. Web pages are indexed by search engines and read on phones without a download.
• It scales. A conversion can run on every file, where hand remediation runs one file at a time.

When you still need the PDF

Some documents have to stay as PDFs: signed forms, print-ready layouts and records you are required to keep unchanged. Keep those, make them accessible at the source where you can, and link the HTML version beside them so nobody is left without a usable copy.

What Savoy does

Savoy converts each PDF on your site into an accessible web page served from your own domain, and scores every page with axe-core, an industry-standard testing tool. It works through a WordPress plugin or one script tag. Review the output before you rely on it, because automatic conversion is not a substitute for checking the pages that matter most. See install options or start with the free report.

This guide is general information, not legal advice. Savoy does not guarantee compliance with any accessibility law. See our Terms of Service.