Why Redacted PDFs Sometimes Fail Accessibility Standards

When you redact a PDF to remove sensitive information, you solve one problem but can inadvertently create another: the redacted document may no longer meet accessibility standards required by law or policy. Even when visible content is properly removed, the underlying accessibility structures that help people with disabilities navigate and understand the document can be damaged or destroyed in the process.

This matters because many organizations are legally required to provide accessible documents under standards like WCAG 2.1 (Web Content Accessibility Guidelines), Section 508 of the Rehabilitation Act in the United States, or the European Accessibility Act. A document that was once fully accessible can become non-compliant after redaction, exposing organizations to legal risk and excluding users who rely on assistive technologies.

This page explains why redaction breaks accessibility, what structures are affected, and how to approach redaction when accessibility compliance matters.

How PDF Accessibility Works

An accessible PDF contains more than just visible text and images. It includes a hidden layer of structural and semantic information that assistive technologies like screen readers use to present content to users who are blind, have low vision, or have cognitive disabilities.

The key accessibility features in a PDF include:

• Tags: A hierarchical structure that defines headings, paragraphs, lists, tables, and other document elements, similar to HTML semantic markup
• Reading order: A sequence that tells screen readers which content to read first, second, and so on, independent of visual layout
• Alternative text: Descriptions for images, charts, and non-text elements that convey their meaning to users who cannot see them
• Table structure: Headers and cell relationships that allow screen reader users to navigate complex data tables
• Form field labels: Programmatic associations between form fields and their descriptive labels
• Document language: Language declarations that help screen readers pronounce content correctly

These features are stored separately from the visible content layer. When you redact visible text or images, the accessibility structures that reference that content often remain intact but broken, or are removed entirely, leaving gaps in the document structure.

Why Redaction Breaks Accessibility Structures

Most PDF redaction tools, including professional software and browser-based tools, focus exclusively on removing visible content. They permanently delete text, images, or vector graphics from the PDF's content stream but do not automatically repair the accessibility layer.

Orphaned Tags and Broken Reading Order

When you redact a paragraph, heading, or list item, the corresponding tag in the document's tag tree may be deleted, but surrounding tags remain. This creates structural gaps: a heading tag might reference content that no longer exists, or the reading order might skip from paragraph 3 to paragraph 7 because paragraphs 4, 5, and 6 were redacted.

Screen readers may announce empty headings, skip over content unpredictably, or present the remaining content in a confusing sequence. Automated accessibility checkers flag these issues as failures under WCAG Success Criterion 1.3.1 (Info and Relationships) and 2.4.6 (Headings and Labels).

Missing Alternative Text

If you redact an image or chart, the alternative text describing that image may remain in the document structure. A screen reader user will hear the description of content that has been visually removed, which can be confusing or, worse, reveal information you intended to redact. Conversely, some redaction processes strip alternative text entirely, leaving other images in the document without descriptions and failing WCAG Success Criterion 1.1.1 (Non-text Content).

Table Structure Damage

Redacting cells in a complex table can destroy the programmatic relationships between headers and data cells. A screen reader user navigating a redacted table may hear header information for cells that no longer exist, or data cells may be presented without their corresponding headers. This violates WCAG Success Criterion 1.3.1.

Form Field Label Disconnection

In fillable PDF forms, redacting labels or instructions can break the programmatic association between form fields and their labels. Screen reader users may encounter unlabeled fields, making the form unusable and failing WCAG Success Criterion 1.3.1 and 3.3.2 (Labels or Instructions).

Language and Metadata Loss

Some redaction workflows strip document metadata, including language declarations. Without a declared language, screen readers may default to the wrong pronunciation rules, making content unintelligible to users. This fails WCAG Success Criterion 3.1.1 (Language of Page).

Common Mistakes When Redacting Accessible PDFs

Organizations that need to both redact content and maintain accessibility often make these errors:

• Assuming visual redaction is sufficient: If you use a tool that only removes visible content, you may leave behind screen readers and redacted text or broken structural tags
• Flattening the PDF: Converting a tagged PDF to an untagged image-based PDF removes all accessibility structures, not just the broken ones. This approach sacrifices accessibility entirely rather than repairing it
• Ignoring accessibility testing after redaction: Many teams redact documents without re-running accessibility checkers or screen reader tests, failing to catch introduced errors before publication
• Not re-tagging after redaction: Even if redaction is done correctly, the resulting document may need to be re-tagged or have its reading order manually adjusted to restore full accessibility
• Using lightweight tools for high-stakes documents: Browser-based and mobile redaction tools rarely handle PDF accessibility structures at all. For government document redaction or legally mandated accessible publishing, specialized software is often necessary

Approaches to Preserve Accessibility When Redacting

If you must redact content from an accessible PDF and maintain compliance with accessibility standards, consider these strategies:

1. Use redaction software that handles tagged PDFs: Professional tools like Adobe Acrobat Pro can remove content while attempting to preserve or repair tag structures. Some tools offer an option to remove tags associated with redacted content while leaving the rest of the tag tree intact.
2. Manually review and repair tags after redaction: After redacting, use the PDF's tag editor to remove orphaned tags, reconnect broken structures, and adjust the reading order. This is time-consuming but necessary for compliance.
3. Re-run accessibility checkers: Use built-in accessibility checkers (such as those in Acrobat Pro or the free PAC 2024 tool from the PDF/UA Foundation) to identify structural issues introduced by redaction, then address each flagged error.
4. Provide alternative text for any newly exposed images: If redaction reveals previously hidden images or creates new visual boundaries, ensure all images have descriptive alternative text.
5. Test with actual screen readers: Automated checkers catch structural errors but not usability problems. Test the redacted document with NVDA, JAWS, or VoiceOver to confirm the reading experience is coherent.
6. Document your process: For organizations subject to accessibility audits, maintain documentation showing that accessibility was considered and tested throughout the redaction workflow.

For documents that require both heavy redaction and strict accessibility compliance, some organizations find it more efficient to recreate the document from scratch using only the non-sensitive information, then tag the new document properly, rather than attempting to repair a heavily redacted file.

When Accessibility and Redaction Conflict

In rare cases, the requirements of accessibility and redaction may conflict. For example, if a document contains a complex data visualization that must be redacted, the alternative text describing that visualization would need to be removed as well, leaving a gap in the accessible reading experience. In such situations, consider whether a text note can be inserted explaining that content was removed for privacy or security reasons, so screen reader users understand the gap is intentional.

Organizations should consult legal and accessibility experts when navigating these conflicts, particularly in contexts like legal discovery, FOIA responses, or medical records release where both accessibility and privacy are legally mandated.

Related guides

Explore more ways to redact PDFs privately, or use the redaction tool above:

• screen readers and redacted text
• government document redaction

Frequently asked questions