Skip to content
elk.solutions

Word and Excel to PDF/UA

A validated PDF or a targeted error message

Illustration of the principle

Word and Excel files often contain more meaning than is visible on the surface. Headings may only be bold, table headers are not always identifiable and images may lack descriptions. A standard PDF export does not reliably preserve that meaning by itself.

The Elk Solutions converter beta examines every DOCX or XLSX file individually. Structure that can be established reliably proceeds to PDF/UA. If the meaning cannot be determined safely, conversion stops with an error message that identifies where repair is needed.

01Observation · illustrative diagram

The symptom: the PDF looks finished, but its structure is uncertain

A visually correct PDF may still be unusable with a screen reader. Possible causes include an ambiguous heading hierarchy, unknown table headers, indeterminate reading order or an image without a description. Damaged or protected source files may also block conversion.

A document without headings is not rejected automatically. The question is always whether its available structure can be established reliably without inventing meaning.

02Recovery view · illustrative diagram

The solution: PDF or error message

The general beta accepts arbitrary DOCX and XLSX files without requiring a fixed document family. DOCX is the more mature route; XLSX is experimental. The conversion has not yet been proven broadly and is open for beta enquiries and integration projects.

Every file follows four steps:

  1. Analyse: inspect content, styles, tables, images and available structure.
  2. Reconstruct or reject the structure: only meaning that can be established reliably proceeds.
  3. Create and test the PDF: check the output technically and structurally.
  4. PDF or error message: supply only a validated PDF; otherwise return an error with its location and repair advice.

What you receive

On success, you receive the validated PDF. The validated status means that veraPDF reports zero failed checks and that the structure check demonstrably belongs to this file. PAC review and visual review each have a separate status.

With a blocked or failed result, there is no downloadable PDF. You do receive a diagnostics.json with the location and repair advice. Possible error codes include heading_hierarchy_uncertain, table_structure_uncertain, structure_validation_failed, conversion_failed and pdfua_validation_failed.

XML or HTML can be produced as an additional output for internal reuse of structure that has been established reliably. The primary outcome remains a PDF/UA or an error message. The beta provides no general repair guarantee for existing PDF files.

Does this pipeline use RenderX XEP?

A formatter migration must demonstrably preserve the structure carried by the source. We therefore compare more than PDF files and follow XML, XSLT, XSL-FO and formatter dependencies as one pipeline.

Can your DOCX or XLSX be converted reliably to PDF/UA?

Provide a representative file and describe the intended integration. We show what can be automated and where the source first needs repair.

Discuss a beta or integration