Adobe Acrobat PDF Accessibility: A Realistic Assessment

Adobe Acrobat Pro is the most widely-used tool for PDF accessibility remediation. But can it actually make your documents fully compliant? This analysis examines what Acrobat can and cannot do, backed by documentation from Adobe itself, accessibility professionals, and real-world experience.

What Adobe Acrobat Pro Can Do

Adobe Acrobat Pro DC includes genuine accessibility capabilities. According to Adobe's official documentation, these include:

• Automated accessibility checking: The Full Check feature tests 32 different accessibility criteria
• Auto-tagging: Can add basic tag structure to untagged PDFs
• Reading Order tool: Visual interface to adjust content reading sequence
• Tags panel: Direct manipulation of document tag structure
• Table Editor: Tools to define table headers and cell relationships
• Alternative text: Ability to add alt text to images and figures
• Form field properties: Can add labels and tooltips to form fields

For simple documents created from accessible source files, Acrobat can be an effective remediation tool. The question is what happens with real-world documents.

Critical Limitation #1: The Checker Doesn't Verify Compliance

According to Minnesota state accessibility coordinators, Acrobat's accessibility checker:

• "Does not check to the State's WCAG 2.1 standard"
• "Can't tell if the information provided is meaningful"
• Cannot distinguish between meaningful alt text and placeholder text like "add alt text here"

Similarly, Pope Tech states: "The automated checker only identifies a portion of potential issues. Manual testing and inspection are always required to ensure full accessibility compliance."

Critical Limitation #2: It Only Detects, Not Validates

According to Pope Tech's accessibility guide:

"The Accessibility Checker automatically checks accessibility issues including if the document is tagged. You should still manually check your tags and document's reading order using the Fix reading order tool. The Accessibility Checker doesn't know if your tags are correct – it just knows they're there."

This means a document can pass Acrobat's accessibility check while still being completely inaccessible to screen reader users. The checker confirms presence, not correctness.

Critical Limitation #3: No Undo for Tag Operations

According to Allyant's comparison of PDF remediation tools:

"Many tasks in Acrobat in working with the Tag tree are complex and time-consuming. Without an 'undo' feature, you may be forced to start over if you make a mistake."

Adobe's own documentation on the Reading Order tool confirms: "Save the document (or a copy of it) before you use the Reading Order tool, as undo-redo isn't supported for all operations."

This limitation significantly increases remediation time, as mistakes require starting over rather than simply undoing.

Critical Limitation #4: Complex Tables Are Extremely Difficult

According to Allyant, "Remediating data tables is a lengthy, inefficient and time-consuming process" in Adobe Acrobat.

Illinois State University's accessibility guide notes: "Adding tags on a cell level in Acrobat is a labor-intensive procedure."

Specific challenges with tables include:

• Tables with merged cells require manual scope and span attributes
• Microsoft Word has no concept of row headers, requiring manual correction
• Multi-level header relationships must be defined individually
• The Table Editor tool exists but is cumbersome for complex structures

Critical Limitation #5: Lists Require Manual Tag Manipulation

According to CommonLook's analysis:

"Acrobat has no tool to create lists—the list structure must be manually added and manipulated within the tags panel, which is a tedious process."

Properly tagged lists require a specific structure: <L> container, <LI> for each item, and <LBody> for the content. In Acrobat, this structure must be built manually in the Tags panel.

Time Requirements: The Real Cost

According to ADA Site Compliance, time requirements vary dramatically based on document complexity:

According to AWS Public Sector Blog, manual remediation typically costs "$1-$4 per page and hours per document."

What Manual Checks Are Required

According to Pope Tech, even after running Acrobat's checker, you must manually verify:

• Headings are marked AND have the correct hierarchy
• Tags are structured properly and in logical reading order
• Lists have correct components (<L>, <LI>, <LBody>)
• Tables have correct components (<Table>, <TR>, <TD>, <TH>)
• Images have meaningful alt text (not placeholders)
• Form fields have programmatically associated labels

Pope Tech recommends testing with an actual screen reader after manual review to confirm tags are announced correctly.

Alternative: Specialized Remediation Tools

Several tools extend or replace Acrobat's accessibility features:

CommonLook PDF

According to WebAIM, CommonLook PDF is "a plug-in for Adobe Acrobat Pro DC to create, evaluate, and repair tagged PDF documents—often more efficiently than Acrobat alone."

Key advantages over Acrobat alone:

• List generation: One-click list structure creation
• Easier tag manipulation: Merging, deleting, reordering tags is simplified
• Standards verification: Tests against WCAG 2.0/2.1, Section 508, and PDF/UA
• Proven workflow: Structured process for 100% compliance

Limitations: Requires Windows, costs approximately $900/year, and you still need Acrobat for initial tagging.

PAC (PDF Accessibility Checker)

A free validation tool that checks against PDF/UA and WCAG standards—something Acrobat's built-in checker cannot do. However, PAC is checking-only; it cannot remediate documents.

AI-Powered Solutions

According to AWS Public Sector Blog, emerging AI solutions can reduce remediation from "$1-$4 per page and hours per document, to cents per page and seconds to minutes per document."

When to Use Acrobat vs. Professional Services

Acrobat May Be Sufficient When:

• Documents are created from accessible source files (Word with proper styles)
• Content is primarily simple text with basic formatting
• No complex tables, forms, or data visualizations
• You have trained staff with accessibility expertise
• Volume is low (fewer than 10-20 documents)

Professional Remediation Is Better When:

• Documents contain complex tables with merged cells or multiple header rows
• PDFs are scanned documents requiring OCR
• Interactive forms need accessible field structures
• High volume of documents needs remediation
• Legal compliance deadlines are approaching (April 2026 for ADA Title II)
• Internal staff lack accessibility training

The Scale Problem

For organizations facing ADA Title II compliance deadlines, the math is challenging. According to AWS:

"This leaves thousands, if not millions, of documents per public entity requiring remediation within the new rule's compliance timeline."

If each document takes hours to remediate manually in Acrobat, and you have thousands of documents, the timeline becomes impossible without automated assistance or professional services.

Recommended Workflow

Based on guidance from Pope Tech and other sources, an effective remediation workflow includes:

1. Start with accessible source files whenever possible (Word, InDesign with proper styles)
2. Run Acrobat's Full Check to identify obvious issues
3. Manually review tags using the Reading Order tool
4. Manually verify reading order for logical sequence
5. Check table structures using the Table Editor or Tags panel
6. Validate with external tools like PAC or CommonLook PDF Validator
7. Test with a screen reader (JAWS, NVDA, or VoiceOver)

How AdaRemediation Differs

AdaRemediation uses AI to automate the tedious aspects of PDF remediation while maintaining quality:

• Automated tagging: Intelligent structure detection beyond Acrobat's auto-tag
• Complex table handling: Automatic header association and scope assignment
• Meaningful alt text: AI-generated descriptions reviewed by humans
• Bulk processing: Remediate hundreds of documents efficiently
• Standards validation: Testing against WCAG 2.1 AA, Section 508, and PDF/UA
• Human review: You can approve or modify all changes before finalizing