Accessible PDF and Word from the HTML you already have.
Accessibility rules such as the European Accessibility Act and Section 508 apply to the documents you send out, not only to your website. PD4ML UA turns well-structured HTML into tagged PDF/UA that screen readers, reflow and accessibility checkers understand.
PD4ML 4.2 tags more of the document, and adds accessible DOCX and RTF, so the Word version of a document is accessible as well.
Structure that assistive technology can follow.
The v42 engine writes more of the HTML's meaning into the PDF's structure tree.
Headings and sections
Headings and sections become the document outline that screen-reader users navigate by.
Tables with header scopes
Header cells carry their scope, so every data cell is read with its row and column headers.
Lists, links and images
Lists keep their nesting, links are tagged with their targets, and images and SVG carry their alternate text.
Formulas, not artifacts
MathML formulas in tagged output (PDF/UA, PDF/A-a) are tagged as Formula with alternate text instead of being hidden as artifacts.
Language and metadata
/Lang is taken from <html lang>, so screen readers use the right language, and custom metadata keeps PDF/A valid.
Strict checking
The PEDANTIC error policy treats possible PDF/UA and PDF/A incompatibilities as errors, so you can stop a non-conforming document before it's sent.
Accessible Word documents.
With the v42 engine and the UA edition, DOCX and RTF output carries the structure that Word's Accessibility Checker and screen readers use.
- Headings use the "heading 1" to "heading 6" styles, so the navigation pane, tables of contents and screen readers find them, and the page looks the same.
- Table header rows are marked as headers and repeat on every page.
- Alternate texts of images and graphics are kept.
- The document language and title are set, so screen readers use the right voice and announce the document properly.
- One HTML source gives you an accessible PDF and an accessible Word file, with nothing to fix up by hand.
Repair the source before it becomes a PDF.
HTML from CMSs and editors often lacks alternate texts or a language. With the DOM API, code can fill the gaps after readHTML() and before any output, for PDF and Word alike.
Merging keeps the result accessible: the PDF merge API combines page ranges of several PDFs and reconciles their accessibility tags.
PD4ML pd4ml = new PD4ML();
pd4ml.useHtmlRenderer(Constants.LayoutEngine.v42);
pd4ml.readHTML(new URL("https://example.com/statement.html"));
Document doc = pd4ml.getDocument();
Element html = doc.getDocumentElement();
if (!html.hasAttribute("lang")) html.setAttribute("lang", "en");
for (Element img : doc.querySelectorAll("img:not([alt])"))
img.setAttribute("alt", ""); // decorative
pd4ml.writePDF(pdfOut, Constants.PDFUA); // tagged PDF/UA
pd4ml.writeDOCX(docxOut); // accessible Word
Features marked v4.2 are part of the PD4ML v4.2.0 development snapshot: download it from the Downloads page or use 4.2.0-SNAPSHOT from the Maven repository. The other features are in the current releases, PD4ML v4.1.2 and v4.0.24. The release notes and What Is New in PD4ML v4.2.0 list every change.
Explore the other improvements
Check your documents for accessibility.
Convert a real document with a free evaluation license and run it through PAC, veraPDF or Word's Accessibility Checker.
