FAQs: HTML to PDF Conversion for Digital Commons Websites

The new HTML‑to‑PDF conversion service is becoming a standard feature of the Digital Commons platform. It allows agencies to replace traditional PDFs with mobile‑friendly, translatable and searchable HTML site pages. HTML content is more accessible, easier to navigate, and aligns with Title II ADA requirements. PDFs often create barriers for screen‑reader users and mobile visitors.

1. What does the PDF‑to‑HTML conversion do?

Most PDFs can be converted into single‑column HTML site pages. HTML pages are easier to edit, work across all devices, support translation, and are significantly more accessible than PDFs. 

2. Is there a demo available?

Yes. You can preview a short video of the website interface and conversion process. The service automatically extracts text, images, and structure from the PDF and generates an HTML page. An AI-generated Auditor Report will be provided for each document to support this process with majority of issues flagged.

3. Will the HTML page replace the PDF?

Yes. Once converted, the new HTML site page replaces the PDF instead of appearing alongside it. 

4. Can I revert an HTML page back to a PDF?

Yes. A converted HTML page can be reverted back to its original PDF at any time.
However, any edits made to the HTML page will be lost during the revert process.

5. What happens to links to the old PDFs?

All existing PDF links will automatically redirect visitors to the new HTML site page. 

6. Which PDFs are excluded from conversion?

• PDF forms – recommended alternative: replace with Webforms.
• Password‑protected PDFs.
• Slide-decks 
• Legal documents that require wet signature should be reviewed and remediated manually. 

7. What requires manual remediation?

All excluded PDFs documents must be reviewed manually to meet WCAG 2.1 AA accessibility standards. A reference guide is available for review of these documents to meet accessibility standards (WCAG 2.1 Level AA). Learn About PDF Accessibility and Remediation

8. Does this guarantee accessibility compliance?

No. While HTML improves accessibility, complex content - such as tables, forms, legal text, and scanned documents -may still require manual review. An AI-generated Auditor Report will be provided for each document to support this process.

9. Will the layout, fonts, or styling be preserved?

Not exactly. The conversion focuses on content accuracy, not visual replication. Fonts, styling, and detailed layout elements may change.

10. How accurate is the conversion? Will content remain intact?

In most cases, yes. Text and images convert cleanly, but complex structures (tables, footnotes, custom formatting) may require minor manual cleanup. An AI-generated Auditor Report will be provided for each document to support this process with majority of issues flagged.

11. What about hyperlinks, bookmarks, or metadata?

Most links and structural markers are preserved, but some complex metadata may not carry over perfectly.

12. Can it convert scanned documents?

Mostly. The system uses OCR for scanned content, but quality depends on the clarity of the original scan. Manual corrections may be required.

13. When will the service be available?

• For Digital Commons websites this service will be available starting March 30, 2026.
• Non‑DC websites after conversion completed for Digital Commons websites.

14. How much does the service cost?

• No cost for Digital Commons websites 
• For agency websites not hosted on Digital Commons, the PDF-to-HTML solution will cost as little as $0.03 per page. Agencies will need to upload the HTML pages to their sites and remove the old PDFs. Delivery details for these sites are still being finalized.

15. Will other file types be supported by this process.

Will other file types be supported in the future?

At this time, the service supports PDFs only. 

16. Suggested Review Process

The recommended review approach is outlined in the Digital Commons guide.