PDF & Document Accessibility — Tagged PDF, Word & PowerPoint Guide

In this tutorial, you'll learn about PDF & Document Accessibility. We cover key concepts, practical examples, and best practices to help you understand and apply this topic effectively.

Accessible PDF and document formats use tagged structure, proper heading hierarchies, alt text for images, and reading order metadata to ensure screen readers and assistive technologies can navigate them as effectively as web pages.

What You'll Learn

By the end of this guide, you'll understand what a tagged PDF is and why it matters, how to create accessible documents in Microsoft Word and PowerPoint, how to remediate existing PDFs using Adobe Acrobat, how to test document Accessibility with screen readers, and how to build an accessible document workflow for your organization.

Why Document Accessibility Matters

PDF is the most common format for distributing reports, whitepapers, and forms. An untagged PDF is a digital image of text — screen readers see a blank page. Governments, educational institutions, and enterprise customers increasingly require WCAG-compliant documents. At DodaTech, Durga Antivirus Pro distributes its security whitepapers as tagged PDFs, and DodaZIP includes accessible help documentation in its installer package.

Document Accessibility Decision Flow

flowchart TD
  A[Source document] --> B{Format}
  B -->|Word| C[Apply styles: Headings, Lists, Alt text]
  B -->|PowerPoint| D[Set reading order, Slide titles, Alt text]
  B -->|InDesign| E[Export tagged PDF]
  C --> F[Save as tagged PDF]
  D --> F
  E --> F
  F --> G[Test with screen reader]
  G --> H{Issues found?}
  H -->|Yes| I[Remediate in Acrobat]
  H -->|No| J[Publish accessible PDF]
  I --> G

{{< callout type="info" icon="sparkles" >}} Prerequisites: Familiarity with Microsoft Office or Adobe InDesign. Basic understanding of WCAG principles and screen-readers. {{< /callout >}}

What Is a Tagged PDF?

A tagged PDF includes a logical structure tree that defines the document's reading order, heading hierarchy, list structures, table relationships, and alt text for images. This structure tree is what screen readers use to navigate the document.

Without tags, a PDF is a paper document rendered as pixels. With tags, it is as navigable as an HTML page:

<!-- Simplified PDF tag structure -->
<TaggedPDF>
  <Document>
    <H1>Durga Antivirus Pro — Security Whitepaper 2026</H1>
    <P>This whitepaper explains the threat detection engine...</P>
    <H2>Heuristic Analysis</H2>
    <P>Our heuristic engine analyzes file behavior in real time...</P>
    <Figure alt="Chart showing 99.7% threat detection rate over 12 months">
      <Image src="chart-detection-rate.png"/>
    </Figure>
    <Table>
      <Caption>Comparison of scan types</Caption>
      <TR>
        <TH>Scan type</TH>
        <TH>Duration</TH>
        <TH>Files checked</TH>
      </TR>
      <TR>
        <TD>Quick scan</TD>
        <TD>2-5 minutes</TD>
        <TD>Common locations</TD>
      </TR>
    </Table>
  </Document>
</TaggedPDF>

Creating Accessible Word Documents

Most PDF Accessibility issues originate in the source document. Fix it in Word first:

### Word Accessibility Checklist

1. **Use built-in heading styles** (Heading 1, Heading 2, etc.) — never use bold + large font as a heading. Word's heading styles map directly to H1-H6 tags in the PDF.

2. **Add alt text to all images** — right-click an image, select "View Alt Text," and write a descriptive alternative. Mark decorative images as decorative.

3. **Use table headers** — select the header row and mark it as "Repeat as header row" in Table Design. Never merge cells in data tables.

4. **Add meaningful link text** — "Click here" is not accessible. Use the full document title as link text.

5. **Set the document language** — go to File > Options > Language and set the editing language.

6. **Use ordered and unordered lists** — use Word's list buttons, not manual hyphens or numbers.

7. **Add a table of contents** — Word's built-in TOC uses heading styles and generates proper navigation in the PDF.

8. **Check reading order** — the Navigation Pane in Word shows the document's outline. Each heading must appear in logical order.

Expected output: A Word document where the Navigation Pane shows a clean hierarchy, every image has alt text, and tables have marked header rows.

Creating Accessible PowerPoint Documents

PowerPoint Accessibility focuses on slide titles, reading order, and alt text:

<!-- PowerPoint Accessibility Markup (conceptual) -->
<Slide>
  <Title>Threat Detection Results — Q2 2026</Title>
  <Content>
    <Paragraph>Durga Antivirus Pro blocked 99.7% of threats this quarter.</Paragraph>
    <Image alt="Bar chart showing 1,247 ransomware, 3,892 phishing, 2,561 trojan detections">
      <src>q2-results.png</src>
    </Image>
  </Content>
  <Notes>Screen reader notes: emphasize the 99.7% success rate</Notes>
</Slide>

PowerPoint Checklist

1. Every slide needs a unique title — Go to Home > Layout and choose a layout with a title placeholder. If the title is visually hidden, use the Accessibility Checker to mark it as a title.

2. Set reading order — Home > Arrange > Selection Pane. The bottom item is read first. Reorder elements from bottom to top in logical reading order.

3. Add alt text to all images, charts, and SmartArt — Right-click > Edit Alt Text.

4. Use table headers — Tables in PowerPoint need the header row identified in the Design tab.

5. Avoid text boxes — Text boxes do not appear in the tagged PDF structure. Use placeholder text or shapes with alt text.

6. Add slide titles to all slides — Even if the slide is a content transition, add a title and hide it visually if needed.

PDF Remediation in Adobe Acrobat

If you receive an untagged PDF, use Adobe Acrobat Pro to remediate:

# Use Acrobat Pro's built-in action wizard:
# 1. Tools > Accessibility > Full Check
# 2. Tools > Accessibility > Add Tags to Document
# 3. Tools > Accessibility > Set Alternate Text
# 4. Tools > Accessibility > Touch Up Reading Order

// Adobe Acrobat JavaScript — auto-tag and check
// Run in Acrobat Pro console
function remediatePDF() {
  // Step 1: Add tags
  this.addTags();
  console.log("Tags added.");

  // Step 2: Set document language
  this.setLanguage("en-US");
  console.log("Language set to en-US.");

  // Step 3: Check accessibility
  var results = this.checkAccessibility({
    check: [
      "TaggedPDF",
      "LogicalStructure",
      "ReadingOrder",
      "AlternateText",
      "DocumentLanguage]
    ]
  });

  console.log("Accessibility check complete.");
  results.forEach(function(r) {
    console.log(r.name + ": " + (r.passed ? "PASS" : "FAIL"));
  });
}

remediatePDF();

Expected output:

Tags added.
Language set to en-US.
Accessibility check complete.
TaggedPDF: PASS
LogicalStructure: PASS
ReadingOrder: PASS
AlternateText: FAIL
DocumentLanguage: PASS

Testing Document Accessibility

Test documents with the same tools you use for web content:

<!-- Test with NVDA:
1. Open the PDF in Adobe Acrobat Reader
2. Enable Read Out Loud: View > Read Out Loud > Activate Read Out Loud
3. Press Ctrl+Shift+V to start reading from current page
4. Navigate headings with H key, tables with T key
5. Listen for:
   - Headings announced with level ("Heading Level 1...")
   - Alt text read for images ("Graphic: ...")
   - Table headers announced with cells
   - Correct reading order (left to right, top to bottom)
-->

Common Mistakes

1. Scanning Paper Documents to PDF

A scanned PDF is an image. Without OCR and tagging, it has no text and no structure. Always run OCR and add tags.

2. Skipping Alt Text in Source Documents

Adding alt text in Acrobat is possible but tedious. Add it in Word or PowerPoint where it is easier to manage.

3. Using Manual Numbering Instead of List Styles

Manually typed "1. 2. 3." does not create list tags in the PDF. Use Word's numbered list feature.

4. Complex Table Structures

Merged cells, nested tables, and blank cells create navigation problems. Keep tables simple with a single header row.

5. No Document Title

A PDF without a document title displays the filename in the title bar. Screen readers announce the filename, which is rarely descriptive.

6. Missing Language Declaration

If the document language is not set, screen readers use the system default language, causing incorrect pronunciation.

7. Relying Solely on Automated Checks

Automated checkers catch structural issues but cannot evaluate whether alt text is meaningful or reading order is logical.

Practice Questions

1. What is a tagged PDF?

A tagged PDF includes a logical structure tree that defines headings, paragraphs, lists, tables, and alt text — enabling screen readers to navigate the document.

2. Why should you fix Accessibility in the source document rather than the PDF?

Source document changes (Word, PowerPoint) are easier to make and maintain. Remediating in Acrobat is time-consuming and must be repeated when the source is updated.

3. What is the minimum number of images that need alt text in a document?

Every informative image needs alt text. Decorative images should be marked as decorative, which produces empty alt text in the PDF.

4. How do you set reading order in PowerPoint?

Home > Arrange > Selection Pane. The bottom item in the pane is read first. Reorder elements from bottom to top to match logical reading order.

5. Challenge: Take an existing 3-page PDF report without tags. Using Adobe Acrobat Pro, add tags, set alt text for all images, verify heading hierarchy, and test with NVDA Read Out Loud. Document every issue you fix.

Real-World Task

Create an accessible Word template for your organization. Include heading styles, a table of contents, alt text placeholders, table header formatting, and language settings. Distribute the template to your team and train them on its use.

FAQ

Try It Yourself

Create an accessible Word document about DodaZIP features, save it as a tagged PDF, and test it:

# DodaZIP — Feature Overview

## Compression Formats

DodaZIP supports ZIP, RAR, 7z, TAR, and GZ formats.

## Encryption

All archives can be encrypted with AES-256 encryption.

## Accessibility Features

- Keyboard shortcuts for all operations
- Screen reader announcements for archive progress
- High-contrast mode for dialogs

Apply Heading 1 and Heading 2 styles. Add an image of the DodaZIP interface with alt text "DodaZIP main interface showing file list and compression options." Save as a tagged PDF and test with NVDA.

What's Next

Congratulations on completing this PDF and Document Accessibility tutorial! Here is where to Go from here:

• Practice daily — Run the Accessibility Checker on every document you create
• Build a project — Create an accessible document template library for your team
• Explore related topics — Learn accessible SVGs and charts next
• Join the community — Discuss with other learners and share your progress

Remember: every expert was once a beginner. Keep coding!