---
title: "Introduction to PDF/UA and auto-tagging"
canonical_url: "https://www.nutrient.io/guides/dws-accessibility/developer-guides/introduction-to-pdfua-and-auto-tagging/"
md_url: "https://www.nutrient.io/guides/dws-accessibility/developer-guides/introduction-to-pdfua-and-auto-tagging.md"
last_updated: "2026-06-09T10:24:29.130Z"
description: "Learn what PDF/UA requires, how auto-tagging works, and how to build a scalable remediation workflow with validation and QA."
---

# Introduction to PDF/UA and auto-tagging

This guide explains how PDF/UA and auto-tagging fit into accessibility pipelines. It also outlines a rollout pattern for production workflows.

## What PDF/UA means in practice

PDF/UA (ISO 14289) defines how a PDF must be structured so assistive technologies can interpret and present content correctly.

A PDF/UA-ready document needs programmatic structure — and not only visual layout — to ensure accessibility. This means:

- Tag headings as headings.

- Tag lists as lists.

- Expose row, header, and cell semantics in tables.

- Mark images as meaningful content or decorative artifacts.

- Keep reading order logical and consistent.

If these semantics are missing, a document can look correct visually but still fail for screen reader users.

## What auto-tagging does

Auto-tagging detects document elements and adds semantic tags to the PDF structure tree.

Typical auto-tagging output includes:

- Heading and paragraph structure.

- List and list-item tagging.

- Table and cell tagging.

- Figure tagging.

- Reading-order normalization.

Auto-tagging helps teams improve accessibility coverage at scale, especially in high-volume document workflows.

## Where auto-tagging helps most

Manual remediation is often too slow and costly for large document sets. Auto-tagging helps teams:

- Reduce repetitive manual tagging work.

- Improve consistency across generated documents.

- Shorten time to publish accessible outputs.

- Standardize structure before downstream validation.

This approach is useful for public sector, education, healthcare, finance, and enterprise document workflows.

## Recommended pipeline

Use the pipeline below as a foundation for compliance workflows:

1. Run auto-tagging on incoming PDFs.

2. Validate PDF/UA conformance.

3. Apply targeted manual fixes for edge cases.

4. Publish outputs and monitor quality over time.

This model combines automation speed with human QA where needed.

## Auto-tagging limits and QA strategy

Auto-tagging is strong for structural detection, but some areas still need human review. For example:

- Alt text quality and context.

- Semantics in complex layouts.

- Domain-specific meaning where visual context matters.

Treat automated tagging and human QA as complementary steps.

## Rollout approach

Use a phased rollout to keep implementation manageable:

- Phase one — Auto-tag and validate your highest-volume document types.

- Phase two — Add exception handling and QA rules.

- Phase three — Integrate accessibility checks into standard release workflows.

Track measurable outcomes — for example, PDF/UA validation pass rate and manual remediation time — to evaluate progress.

## Next steps

- Refer to the [auto-tag PDFs](https://www.nutrient.io/guides/dws-accessibility/developer-guides/auto-tag-pdfs.md) guide for request patterns.

- Refer to the [accessibility best practices](https://www.nutrient.io/guides/dws-accessibility/developer-guides/accessibility-best-practices.md) guide for a QA checklist.

- Refer to the [DWS Accessibility operational guides](https://www.nutrient.io/guides/dws-accessibility.md#essential-guides) for pricing, security, and support.
---

## Related pages

- [Accessibility best practices](/guides/dws-accessibility/developer-guides/accessibility-best-practices.md)
- [Auto-tag PDFs via API](/guides/dws-accessibility/developer-guides/auto-tag-pdfs.md)
- [DWS Accessibility API developer guides](/guides/dws-accessibility/developer-guides.md)