How to Make a PDF Section 508 Compliant

How to Make a PDF Section 508 Compliant starts with the source file and ends with testing. This guide gives clear steps you can follow whether you will fix the original Word, PowerPoint or an existing PDF.

What Section 508 requires for PDFs

Section 508 requires electronic content to be accessible. For PDF content that generally means meeting the same accessibility success criteria found in WCAG and following the technical PDF/UA rules. Practically, that translates to a tagged document structure, readable text, correct reading order, alternative text on images and labelled form fields.

Decide: fix the source file or remediate the PDF

Choose the faster path before you start. If you have the original Word or InDesign file and you will update the document often, fix the source and export an accessible PDF. If you only have the final PDF, remediate the PDF directly.

Use the source when you can. Styles, headings and semantic markup are far easier to get right in the source file. Remediation in a PDF is slower and often requires manual tagging and reading order fixes.

Before you export: prepare the source file

Fixing the source reduces work later. Follow these rules in Word, PowerPoint or InDesign.

• Use built-in heading styles for structure. Do not use bold or font size alone to mark headings.
• Write descriptive link text that makes sense out of context.
• Add alternative text for every meaningful image. Mark decorative images as decorative.
• Use real tables only for tabular data and mark header cells with the table header property.
• Use native form fields when you need fillable forms. Provide labels and tooltips.
• Set the document language in the file properties.
• Avoid scanned pages unless you run OCR and then tag the text.

When you export from Word or InDesign, enable document structure tags or accessibility options so the PDF includes tags.

Remediate an existing PDF: step-by-step (Adobe Acrobat Pro)

Adobe Acrobat Pro is a common tool for remediation. Follow this practical workflow.

1. Run the Accessibility Checker to get a list of issues. Use it as your starting map.
2. Autotag the document if tags are missing. Autotagging helps but often needs manual correction.
3. Set the document language in Document Properties so screen readers use the right voice.
4. Open the Reading Order tool or Tags pane to inspect structure. Confirm headings are tagged as H1, H2 and so on.
5. Add or edit alternative text for images. Mark purely decorative images as artifacts or set role=“Figure” with empty alt text.
6. Fix reading order. Use the Order panel to move content blocks into the logical sequence for linear reading.
7. Label form fields. Add accessible names and tooltips and set a correct tab order for keyboard users.
8. Check tables. Ensure header cells are marked and that complex tables have a clear reading order.
9. Remove or adjust security settings that block copying or reading by assistive tech.
10. Run the full Accessibility Checker again and resolve the remaining issues.

After remediation, save a tagged PDF and create bookmarks for long documents to aid navigation.

Testing and validation

Automated tools find many issues but not all. Combine automated checks with manual tests.

Automated tools

• Use Acrobat’s Accessibility Checker for an initial pass.
• Run a PDF/UA validator such as PAC to check technical conformance.

Manual tests you can run in 10 minutes

• Keyboard navigation: tab through the document and all form fields. Ensure focus order is logical.
• Screen reader pass: open the file in NVDA or VoiceOver and listen for correct headings, alt text and reading order.
• Reading order: verify the content reads in document order not visual order.
• Links and tables: follow links and confirm table headers are announced.

Practical test script for a screen reader

This short script finds the most common failures.

1. Open PDF in a screen reader. Scan headings. If headings are missing or out of order, tag them correctly.
2. Move to each image. Confirm alt text reads or the image is skipped when decorative.
3. Tab through every form field. Confirm each field has a label and meaningful tooltip.
4. Navigate tables. Confirm header cells are announced when moving through table rows.

Common mistakes to avoid

• No tags or incomplete tags after conversion from Word or PowerPoint.
• Decorative images left with empty alt text not marked as artifacts or left unmarked.
• Wrong reading order caused by layered page layout or text boxes.
• Form fields created as flat graphics rather than interactive fields.
• Security settings that block assistive technology from accessing content.

Minimum Section 508 PDF checklist

• Document language set in file properties.
• Document is tagged and logical structure matches visual order.
• All meaningful images have alt text or marked as decorative.
• Headings use proper heading tags. No heading text styled only with font changes.
• Links are descriptive and avoid vague text like “click here”.
• Form fields have accessible names and correct tab order.
• Tables use header cells and present a clear reading order.
• No security restrictions that stop assistive tech from reading content.

When to hire a specialist

Hire a specialist when the PDF is long, includes complex tables or contains scanned images with many pages. Also hire help when you must meet a formal Section 508 or PDF/UA conformance report for procurement documentation.

Tools and resources

• Adobe Acrobat Pro for tagging, editing alt text, reading order and form field labels.
• PAC (PDF Accessibility Checker) for PDF/UA validation.
• NVDA and VoiceOver for screen reader testing.
• Use the accessibility checker built into Word and PowerPoint before exporting.

Follow this workflow and keep a short checklist by your desk. That habit will cut remediation time and give you PDFs that meet Section 508 expectations.