Do PDFs Require Tags for Accessibility?

A PDF can look polished, open correctly, and still be unusable to a screen reader user. That is why the question, do PDFs require tags, matters to any organization that publishes forms, reports, policies, course materials, meeting packets, or public records online. Tags provide the structural information assistive technology needs to interpret a document in a meaningful order.

For most public-facing documents, the practical answer is yes: PDFs need properly applied tags to be accessible. Tags alone do not make a PDF compliant, but an untagged PDF is usually a serious accessibility barrier and will commonly fail an accessibility review.

Do PDFs Require Tags Under Accessibility Standards?

The ADA does not contain a sentence that says every PDF must be tagged. Instead, ADA obligations generally require covered organizations to provide people with disabilities equal access to information, services, and digital content. When a PDF is the way an organization provides essential information, an inaccessible PDF can prevent that equal access.

Technical accessibility standards make the need clearer. WCAG applies to web content, including downloadable PDF documents made available through a website. WCAG success criteria concerning information and relationships, reading order, headings, link purpose, images, tables, and forms all depend on a document having usable structure. In a PDF, that structure is generally communicated through tags.

For federal agencies and many federal contractors, Section 508 is especially relevant. The revised Section 508 standards incorporate WCAG Level A and AA requirements. State and local governments, public schools, higher education institutions, and organizations receiving public funding may also have state-level requirements, procurement terms, or policies that require accessible electronic documents.

A tagged PDF is not automatically compliant. It is, however, the expected technical foundation for a PDF that must work with screen readers and other assistive technologies.

What PDF Tags Actually Do

PDF tags are not visible labels added for search engines. They are behind-the-scenes semantic markup that identifies what each part of a document is and how it relates to other content.

A properly tagged document can identify a title, headings, paragraphs, lists, tables, table headers, links, figures, form fields, and language changes. It also establishes a logical reading order. A screen reader can then announce headings as headings, move through lists correctly, identify table headers, and communicate the purpose of links and controls.

Without tags, a screen reader may encounter a PDF as an undifferentiated stream of text or read content in an incorrect order. A two-column newsletter may jump from the first line in the left column to the first line in the right column. A table may become a confusing sequence of disconnected values. An image-only scan may have no readable content at all.

This is not a minor usability issue. If a resident cannot read a public notice, a student cannot access a course handout, or a customer cannot complete a required form, the organization has created a barrier to an essential service or transaction.

Tags support navigation, not just reading

Screen reader users often navigate a long document by headings, links, lists, form controls, or tables. Tags make that navigation possible. For a 50-page policy manual or board packet, this structure can determine whether the document is practical to use.

Tags also support accessibility checkers and remediation workflows. Automated tools can identify many structural concerns, but a human reviewer must still confirm that the tags accurately reflect the document’s meaning.

When an Untagged PDF May Be Acceptable

There are limited cases where an untagged PDF may not need full remediation. The key question is whether the document is active, necessary, and available as the only way to obtain information or complete a task.

An older historical document in an archive may be handled differently if it is not needed for a current service, program, or transaction. Even then, the organization should provide an accessible alternative or a documented process for supplying one upon request. Labeling a document as archival does not remove every obligation, especially when the file remains prominently available and relevant to the public.

A PDF may also be less problematic when the same complete information is available in an accessible HTML page. But the equivalent must actually be equivalent. A short web summary does not replace a detailed PDF application, meeting agenda, technical report, or form.

The safer operational standard is straightforward: if a PDF is published for public use, treat it as content that must be accessible unless your compliance team has documented a valid exception and an alternative format process.

Tagged Does Not Mean Accessible

Many document authors make a common mistake: they run an accessibility checker, see that the document is tagged, and assume the work is complete. Tags can be present but inaccurate, incomplete, or meaningless.

For example, a visual heading formatted with large bold text may be tagged as a paragraph rather than a heading. A list may be represented as plain paragraphs with bullet characters. A data table may lack header cells, preventing a screen reader from associating values with their row and column headings. A decorative image may be announced unnecessarily, while an informative chart may have no text alternative at all.

A compliant PDF also needs an accurate document title, a declared primary language, sufficient color contrast, readable text, meaningful link text, accessible form labels, and a logical tab order. Security settings must not interfere with assistive technology access. If the PDF contains scanned pages, optical character recognition must produce accurate text before meaningful tagging can begin.

PDF/UA, the PDF accessibility standard, is a useful technical target for document production and remediation. It addresses many tagged-PDF requirements, but it does not replace testing against applicable WCAG and Section 508 criteria or reviewing the actual user experience.

How to Create Accessible Tagged PDFs

Accessibility is easier and less expensive when it begins in the source document. Authors should use real heading styles, built-in list tools, proper table structures, descriptive link text, and alternative text for meaningful images before exporting to PDF.

A practical production workflow includes four distinct controls:

• Create source files with semantic styles and accessible content from the start.
• Export to PDF using settings that preserve document structure and accessibility information.
• Run an automated accessibility check to identify missing tags, titles, language settings, contrast concerns, and other detectable issues.
• Review the final PDF manually with keyboard navigation and a screen reader or qualified accessibility tester.

Do not rely on a visual review alone. A document can appear perfect on screen while presenting a completely different, disordered experience to assistive technology.

For complex documents, use a professional PDF remediation tool or a qualified remediation specialist. Tables, fillable forms, multi-column layouts, engineering drawings, legal documents, and scanned records often require more than a basic export-and-check process.

Managing PDF Accessibility in WordPress

WordPress teams often focus on page and post accessibility while overlooking the document library. That creates a gap: an accessible webpage can still link to inaccessible PDFs that contain the actual policy, instructions, application, or report the visitor needs.

Start by inventorying PDFs in the media library and linked document repositories. Prioritize files that support high-traffic pages, required forms, public notices, enrollment, employment, payments, healthcare, education, or government services. Replace inaccessible legacy files with accessible HTML where that is the better user experience, or remediate the PDF when retaining its layout and print format is necessary.

A recurring audit process is more effective than a one-time cleanup. New files are frequently uploaded by different departments, agency clients, instructors, or content editors. Publishing controls, documented authoring standards, and accessibility review responsibilities prevent the document backlog from returning.

WP ADA Compliance Check can support this broader workflow by scanning WordPress content and identifying accessibility issues across site assets, including PDFs. The operational goal is not merely to generate a report. It is to identify the affected file, assign remediation, verify the correction, and prevent inaccessible documents from being published again.

A Better Standard for Document Publishing

Treat every PDF as part of the user journey, not as a separate attachment. If a visitor needs the information to understand a service, make a decision, submit a form, or meet a deadline, the document deserves the same accessibility controls as the page that links to it.

Proper tags are the starting point for that control. Build them into authoring and publishing workflows, verify the results, and provide an accessible path before a user has to ask for one.