HTML vs. PDF remediation
For some documents, converting to an HTML page is cheaper, more accessible, and more maintainable than remediating the PDF. The decision is per-document.
The decision frame
Not every PDF needs to be remediated. Some documents are better converted to an HTML page on the entity's website. HTML is inherently more accessible than PDF: it inherits the page-level accessibility of the site, it works automatically with assistive technology, it adapts to screen size, and it is searchable and crawlable.
The decision is not "HTML is always better." It is per-document. A 4-page board agenda republished weekly is a strong HTML candidate. A 200-page audited financial report with required attestation pages, signatures, and a specific layout for the auditor of record is not.
When HTML is the better choice
HTML conversion is the better answer when one or more of these conditions hold:
- Frequently updated content. Class schedules, staff directories, hours of operation, current notices. Republishing as PDF each cycle creates repeated remediation work; an HTML page is updated in place.
- Content that is essentially text. Policies, FAQs, procedures, simple lists. PDF adds no value over HTML for text-only content; it just creates a less accessible delivery format.
- Content meant to be linked into. Sections of a long document that constituents need to bookmark or share. HTML supports per-section URLs; PDF does not, in a way that survives downloads.
- Mobile-relevant content. PDFs do not reflow well on phones. Content people will read on a phone (instructions, notices, contact information) is best as responsive HTML.
- Short documents being remediated from scratch. If a 4-page scanned PDF needs OCR and full tagging, the remediation cost is comparable to retyping the content as an HTML page. The HTML version is more accessible and more maintainable.
When PDF remediation still makes sense
PDF is the right format, and remediation is the right approach, when one or more of these conditions hold:
- Layout is essential. Forms with specific field positions, designed materials where typography and layout carry meaning, certificates, official notices that must look a specific way.
- The document is a discrete artifact of record. Audited financial statements, accreditation submissions, board-adopted policies in their final form. The document is meant to be downloaded, archived, and referenced as a unit.
- Signatures, seals, or formal authentication are part of the document. Notarized documents, formally signed agreements, certified records.
- Long-form content that benefits from page-based reading. Books, manuals, technical reports where users want to print or read offline.
- The document is already accessible PDF and reasonably current. Don't convert what's already working.
Decision factors to weigh
| Factor | Favors HTML | Favors PDF remediation |
|---|---|---|
| Update frequency | Updates often | Stable, version-fixed |
| Layout importance | Text-dominant | Layout carries meaning |
| Length | Short (1 to 10 pages) | Long, with reference structure |
| Reading context | Read on screen, possibly mobile | Downloaded for offline use |
| Recordkeeping role | Reference content | Document of record |
| Source state | Scanned legacy PDF without source file | Born-digital with usable source |
| Cost comparison | Remediation more expensive than retyping | Remediation cheaper than recreating |
Ongoing maintenance implications
The maintenance picture differs sharply between the two formats.
HTML
Once converted, updates happen in the CMS. Editors who can write a webpage can update the content. No specialized tooling, no per-update remediation, no version-management concerns. Accessibility is largely inherited from the site's templates.
Every update is a new document. If the authoring workflow does not produce accessible PDFs by default, every update produces a new remediation task. For documents on a weekly or monthly publication cycle (board agendas, meeting packets, athletic schedules), this is real ongoing labor.
The corollary: for PDFs that will keep being republished, the highest-leverage accessibility investment is in the authoring workflow, not in retroactive remediation of past versions.
Archive and recordkeeping considerations
Public records laws, retention schedules, and accreditation requirements typically obligate the entity to retain documents of record in fixed form. A board-adopted policy, a final audited financial statement, an accreditation submission as filed: all are documents of record. Converting these to HTML for accessibility purposes does not satisfy the records-retention obligation unless the HTML is itself preserved as the record.
Two common approaches reconcile accessibility with records retention:
- HTML for public access, PDF for the record. Publish the HTML version as the working access copy, retain the PDF (remediated to the extent reasonable) as the recordkeeping copy. Link both from the same landing page so users can choose.
- Accessible PDF as the record. Invest in PDF remediation for the documents that must be retained in PDF form. Treat HTML conversion as a quality-of-access enhancement rather than a substitute.
The right approach depends on the entity's records retention policy, accreditation requirements, and the specific document type. Consult counsel or the records management function on documents where retention obligations are unclear.