> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/core/accessibility/pdfua.md).

# PDF Accessibility Guide with Apryse SDK

Convert generic PDF documents to PDF/UA (ISO 14289-1) with our API. Make your documents accessible to assistive technology. Choose the version and conformance level easily. Get started with Apryse SDK

{% hint style="info" %}
**Requirements**

*These packages are required to use these features in production. Trial keys have unlimited access to all features*

<a href="https://apryse.com/capabilities#Accessibility" class="button primary">Package: Accessibility</a><a href="/core/learn-more/modules.md#data-extraction-module" class="button primary">Module: Data Extraction</a><a href="https://showcase.apryse.com/pdfua-auto-tagging" class="button primary">Live demo</a>
{% endhint %}

## Introduction to PDF Accessibility

Ensuring PDFs are accessible is critical for making content available to all users, including those who rely on assistive technologies like screen readers. Accessibility compliance follows PDF/UA (ISO 14289-1) and WCAG standards, making documents more structured and navigable.

The Apryse SDK provides tools to help automate accessibility compliance with the AutoTagging feature, which automatically applies semantic structure to PDFs, ensuring they are properly formatted for screen readers.

## Why PDF Accessibility Matters

* Legal Compliance → Meet WCAG requirements and reduce legal risks from government mandates such as the European Accessibility Act
* Best Practices → Ensure PDFs are structured for assistive technologies, making content truly accessible
* Inclusivity → Broaden access to content for users with visual impairments.

## Workflows for Creating Accessible PDFs

### Converting a Structured Document (e.g., Word) to an Accessible PDF

* If your content is already structured—such as a Word document with headings, tables, and alt text for images—the best approach is to convert it to a tagged PDF while preserving its accessibility information.
* Ensure the source document is properly structured.
* Convert the document using Apryse SDK.
* Verify accessibility using a PDF reader or checker.

### AutoTagging an Existing PDF with Manual Touch-Ups

* If you have an unstructured or scanned PDF, you can use AutoTagging to automatically apply accessibility tags. Since some document elements require human validation, this process typically involves:
* AutoTagging the document using Apryse SDK.
* Reviewing the tagged PDF for accuracy.
* Manually adjusting elements where needed (e.g., complex tables, reading order).
* This method significantly reduces the manual effort while ensuring compliance with accessibility standards.

### Generating an Accessible PDF from Templates

If you frequently create similar documents, using pre-tagged templates ensures accessibility from the start. This method is ideal for generating accessible PDFs programmatically while maintaining consistency.

#### How It Works:

1. Create a structured template with built-in accessibility tags (e.g., headings, tables, alt text for images).
2. Use the Apryse SDK to dynamically populate content while preserving accessibility structure.
3. Export the final document as a fully tagged PDF ready for assistive technologies.

## Resources

[Top 5 things you need to know about updating your UI to WCAG-compliance](https://apryse.com/blog/webviewer/wcag-compliance-ui)

[The European Accessibility Act and Beyond: The Future of Digital Accessibility](https://apryse.com/blog/european-accessibility-act-strategies-compliance)

[Scaling Document Accessibility with Apryse’s Auto-tagging Solution](https://apryse.com/blog/document-accessibility-with-auto-tagging)

[Auto-tagging for PDF/UA – Improving Accessibility for all using the Apryse SDK](https://apryse.com/blog/auto-tagging-pdf-ua-compliance)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.apryse.com/core/accessibility/pdfua.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.