What PDF/UA standards does IronPDF support?

IronPDF supports both PDF/UA-1 (ISO 14289-1) and PDF/UA-2 (ISO 14289-2:2024). Use SaveAsPdfUA to convert an existing PDF, or RenderHtmlAsPdfUA to generate a compliant document directly from HTML.

How do I convert an existing PDF to PDF/UA with IronPDF?

Load the document with PdfDocument.FromFile and call pdf.SaveAsPdfUA("output.pdf") . IronPDF adds tagged structure, reading order, and metadata required for PDF/UA compliance.

What makes a PDF/UA document different from a regular PDF?

PDF/UA documents contain machine-readable structure: tagged reading order, heading hierarchy, image alt text, and language metadata. These allow screen readers and assistive technology to interpret the document. A visually styled PDF without these tags fails accessibility audits.

How do I validate that a PDF is PDF/UA compliant?

Use the veraPDF Conformance Checker, a free open-source tool that tests against both PDF/UA-1 and PDF/UA-2 standards and reports specific conformance failures. It can be integrated into automated pipelines as a compliance checkpoint.

The C# PDF Library

Q: Can IronPDF make a scanned PDF accessible?

Not fully. IronPDF tags structures it can identify, but cannot manufacture meaning absent from the source. A scanned image with no text layer, missing alt text, or a heading-free layout will still fail PDF/UA conformance. Well-structured source content is a precondition.

Explore IronPDF Start Free Trial

HTML to PDF

Online Demo See All Code Examples

using IronPdf;

// Disable local disk access or cross-origin requests
Installation.EnableWebSecurity = true;

// Instantiate Renderer
var renderer = new ChromePdfRenderer();

// Create a PDF from a HTML string using C#
var pdf = renderer.RenderHtmlAsPdf("<h1>Hello World</h1>");

// Export to a file or Stream
pdf.SaveAs("output.pdf");

// Advanced Example with HTML Assets
// Load external html assets: Images, CSS and JavaScript.
// An optional BasePath 'C:\site\assets\' is set as the file location to load assets from
var myAdvancedPdf = renderer.RenderHtmlAsPdf("<img src='icons/iron.png'>", @"C:\site\assets\");
myAdvancedPdf.SaveAs("html-with-assets.pdf");

using IronPdf;

// Disable local disk access or cross-origin requests
Installation.EnableWebSecurity = true;

// Instantiate Renderer
var renderer = new ChromePdfRenderer();

// Create a PDF from a HTML string using C#
var pdf = renderer.RenderHtmlAsPdf("<h1>Hello World</h1>");

// Export to a file or Stream
pdf.SaveAs("output.pdf");

// Advanced Example with HTML Assets
// Load external html assets: Images, CSS and JavaScript.
// An optional BasePath 'C:\site\assets\' is set as the file location to load assets from
var myAdvancedPdf = renderer.RenderHtmlAsPdf("<img src='icons/iron.png'>", @"C:\site\assets\");
myAdvancedPdf.SaveAs("html-with-assets.pdf");

PM >

Install-Package IronPdf

USE CASES

How to Create Accessible PDF/UA Documents in C#

Curtis Chau

Updated: July 5, 2026

When a law or procurement rule says a document must be accessible, appearance is no longer the test. PDF/UA is the accessibility standard for PDF, and IronPDF exports to both PDF/UA-1 (ISO 14289-1) and PDF/UA-2 (ISO 14289-2:2024). What separates a compliant file from a styled one is machine-readable structure: a tagged reading order, heading hierarchy, image alt text, and language metadata that let a screen reader interpret the page. That structure is what auditors check.

Government and public-sector documents

Section 508 of the Rehabilitation Act is the clearest driver. Any agency or contractor publishing public forms, notices, or reports owes accessible output, and an existing file converts in one call:

using IronPdf;

var pdf = PdfDocument.FromFile("notice.pdf");
pdf.SaveAsPdfUA("notice-pdfua.pdf");

using IronPdf;

var pdf = PdfDocument.FromFile("notice.pdf");
pdf.SaveAsPdfUA("notice-pdfua.pdf");

Imports IronPdf

Dim pdf = PdfDocument.FromFile("notice.pdf")
pdf.SaveAsPdfUA("notice-pdfua.pdf")

Imports IronPdf

Dim pdf = PdfDocument.FromFile("notice.pdf")
pdf.SaveAsPdfUA("notice-pdfua.pdf")

Regulated-industry delivery

Healthcare, finance, insurance, and education all face accessibility mandates for customer-facing documents: statements, policy documents, explanations of benefits. Exporting these as PDF/UA satisfies the obligation at generation time rather than as a later cleanup.

Bringing legacy archives into compliance

Organizations sitting on large back-catalogs of inaccessible PDFs can batch-convert them. The conversion keeps content intact while adding the structures PDF/UA requires, so a backlog collapses into a loop over SaveAsPdfUA.

Accessible documents from web content

Generate compliant PDFs straight from HTML, suited to new documents or dynamic web-app output:

var renderer = new ChromePdfRenderer();
var pdf = renderer.RenderHtmlAsPdfUA(@"
    <!DOCTYPE html>
    <html>
    <head><title>Annual Report 2025</title></head>
    <body>
        <h1>Overview</h1>
        <p>Summary text.</p>
    </body>
    </html>");
pdf.SaveAs("report-pdfua.pdf");

var renderer = new ChromePdfRenderer();
var pdf = renderer.RenderHtmlAsPdfUA(@"
    <!DOCTYPE html>
    <html>
    <head><title>Annual Report 2025</title></head>
    <body>
        <h1>Overview</h1>
        <p>Summary text.</p>
    </body>
    </html>");
pdf.SaveAs("report-pdfua.pdf");

Dim renderer As New ChromePdfRenderer()
Dim pdf = renderer.RenderHtmlAsPdfUA("
    <!DOCTYPE html>
    <html>
    <head><title>Annual Report 2025</title></head>
    <body>
        <h1>Overview</h1>
        <p>Summary text.</p>
    </body>
    </html>")
pdf.SaveAs("report-pdfua.pdf")

Dim renderer As New ChromePdfRenderer()
Dim pdf = renderer.RenderHtmlAsPdfUA("
    <!DOCTYPE html>
    <html>
    <head><title>Annual Report 2025</title></head>
    <body>
        <h1>Overview</h1>
        <p>Summary text.</p>
    </body>
    </html>")
pdf.SaveAs("report-pdfua.pdf")

This holds only when the source is already accessible: semantic elements, a proper heading hierarchy, alt text on images, logical flow, and a meaningful metadata title (itself a compliance requirement).

Multilingual accessibility

The naturalLanguages parameter on SaveAsPdfUA records the document's language, which screen readers need to pronounce content correctly. It matters for anyone publishing in more than one.

Where compliance still depends on the source

IronPDF handles many structural requirements automatically, but cannot invent accessibility absent from the source. A scanned image with no text layer, missing alt text, or a flat heading-free document will still fail. Tagging structures what it can find; it does not manufacture meaning. Treat well-structured source as a precondition.

Validating the result

Confirm compliance with the veraPDF Conformance Checker, a free open-source tool that tests against both PDF/UA-1 and PDF/UA-2 and reports specific issues. Wiring it into an automated pipeline turns accessibility into a checkpoint.

A gate, not an afterthought

PDF/UA is not a styling option or a file-size tweak. It decides whether every reader, not only a sighted one, can use the document, which is why it stays mandatory in regulated, public, and customer-facing work. Build it in as a gate, and the obligation is met before anyone asks.

Curtis Chau

Chat with engineering team now

Technical Writer

Curtis Chau holds a Bachelor’s degree in Computer Science (Carleton University) and specializes in front-end development with expertise in Node.js, TypeScript, JavaScript, and React. Passionate about crafting intuitive and aesthetically pleasing user interfaces, Curtis enjoys working with modern frameworks and creating well-structured, visually appealing manuals.

...