Blog

Do I Need to Make My PDF Files Accessible?

TestParty
TestParty
October 3, 2025

"Our website is accessible, but what about all our PDFs?" This question comes up constantly—and for good reason. Organizations often have hundreds or thousands of PDF documents on their sites: annual reports, product catalogs, application forms, policies, and more. Making all of these accessible can seem overwhelming.

But here's the reality: if your PDFs are published on your website and provide important information or functionality, they generally need to be accessible under the same laws that apply to your web content.

Q: Do I need to make my PDF files accessible?

A: Yes, if your PDFs are publicly available on your website and you're subject to accessibility laws (ADA, Section 508, EAA), they typically need to be accessible. PDFs are considered web content when published online, and the same accessibility requirements apply. This means proper structure, reading order, alt text for images, and screen reader compatibility.

Why PDFs Are Included

PDFs Are Web Content

When a PDF is published on a website, it becomes web content. The W3C's Web Content Accessibility Guidelines apply to "all web content," and courts have consistently interpreted this to include downloadable documents.

The logic is straightforward: if someone visits your website to access information, that information should be accessible regardless of format. A blind user can't read an inaccessible PDF any more than they can use an inaccessible web page.

Legal Landscape

Americans with Disabilities Act (ADA): While the ADA doesn't specifically mention PDFs, courts have ruled that website accessibility requirements extend to downloadable content. Settlement agreements routinely require accessible PDFs.

Section 508: For federal agencies and contractors, Section 508 explicitly requires that electronic documents—including PDFs—be accessible. The standard references WCAG 2.0 Level AA.

European Accessibility Act (EAA): Applies to documents offered as part of services, requiring accessibility conformance.

State Laws: Many state accessibility laws (California's Unruh Act, New York State laws) have been applied to PDF accessibility in settlements and complaints.

Real Consequences

Organizations have faced legal action over inaccessible PDFs:

  • Universities sued for inaccessible course materials
  • Financial institutions challenged over inaccessible statements and forms
  • Government agencies required to remediate document libraries
  • Retailers facing complaints about inaccessible product information

The National Federation of the Blind and other advocacy organizations actively pursue PDF accessibility issues.

What Makes a PDF Accessible?

Accessible PDF Requirements

An accessible PDF includes:

Tagged Structure: PDF tags identify headings, paragraphs, lists, tables, and other structural elements. Tags are the PDF equivalent of HTML elements—they tell screen readers what the content is.

Reading Order: Content must flow in a logical sequence. What looks ordered visually might not read correctly for screen readers if the underlying structure is wrong.

Alternative Text: Images in PDFs need alt text, just like on web pages. Charts, graphs, and informational images must have descriptions.

Accessible Tables: Tables need proper header associations so screen readers can convey row and column relationships.

Form Field Labels: Interactive forms need labeled fields so users know what information to enter.

Document Properties: Language must be specified, and metadata should include a descriptive title.

Navigational Aids: Bookmarks and a linked table of contents help users navigate longer documents.

Appropriate Contrast: Text must have sufficient contrast against backgrounds, and content must be readable when zoomed.

Inaccessible vs. Accessible

Inaccessible PDF characteristics:

  • Scanned image with no text layer
  • No tags or improper tag structure
  • Images without alt text
  • Tables that don't identify headers
  • Reading order that jumps around
  • Forms without labels

Accessible PDF characteristics:

  • Real text that can be selected and searched
  • Complete tag structure matching document organization
  • All images described appropriately
  • Tables with header relationships defined
  • Logical reading sequence
  • Fully labeled interactive elements

Who Must Comply?

Definitely Required

Federal Government Agencies: Section 508 requires all federal electronic content to be accessible. This is non-negotiable and actively enforced.

Federal Contractors: If you receive federal funding or contracts, Section 508 requirements extend to you.

State and Local Government: Many states have adopted Section 508 or similar standards for state agencies.

Educational Institutions: Schools receiving federal funding must ensure equal access, which courts have interpreted to include accessible documents.

Large Employers: Title III of the ADA covers "places of public accommodation," which courts increasingly interpret to include websites and their downloadable content.

Likely Required

Any Business with a Website: If you're subject to ADA website accessibility requirements, your PDFs are probably included. While no explicit federal regulation says "businesses must have accessible PDFs," the trend in litigation and settlements clearly points in this direction.

Healthcare Providers: HIPAA-covered entities handling patient information face heightened scrutiny for accessible communications.

Financial Institutions: Banking regulations and settlement agreements have established expectations for accessible statements, disclosures, and forms.

The Practical Reality

Even if you're not absolutely certain you're legally required to have accessible PDFs, consider:

  • User needs: People with disabilities need to access your content regardless of format
  • Risk mitigation: Inaccessible PDFs are an obvious target for accessibility complaints
  • Inclusion: Accessible documents benefit many users, including those using mobile devices or in challenging environments
  • SEO: Tagged, searchable PDFs perform better in search results

Which PDFs Need to Be Accessible?

Prioritize by Impact

Not all PDFs are equally important. Focus accessibility efforts on:

Critical First:

  • Application forms and registration documents
  • Contracts and legal agreements
  • Financial statements and disclosures
  • Product information and specifications
  • Policies affecting user rights
  • Educational materials and course content

Important:

  • Annual reports and investor information
  • Marketing materials actively promoted
  • Technical documentation
  • User guides and manuals

Lower Priority:

  • Archived historical documents (consider marking as not accessible with contact for accessible format)
  • Superseded versions of documents
  • Internal documents accidentally made public

Reasonable Accommodations

For organizations with massive document libraries, full remediation may take time. In the interim:

  • Provide contact information for requesting accessible formats
  • Offer HTML alternatives for key content
  • Prioritize remediation by user impact and request frequency
  • Add accessibility statements acknowledging limitations and timeline

The Department of Justice has indicated that having a process for providing accessible alternatives can demonstrate good faith while full remediation is underway.

Creating Accessible PDFs

From the Source

The easiest accessible PDFs come from accessible source documents:

Microsoft Word:

  • Use built-in heading styles
  • Add alt text to images
  • Use table features for tabular data
  • Don't use text boxes for layout
  • Run the Accessibility Checker before exporting
  • Export using "Create PDF from Document" with tagging enabled

Adobe InDesign:

  • Use paragraph styles mapped to tags
  • Set reading order in Articles panel
  • Add alt text to graphics
  • Export with Create Tagged PDF option

Google Docs:

  • Use heading styles and built-in lists
  • Add alt text via right-click on images
  • Download as PDF (tagging is automatic)

Fixing Existing PDFs

For PDFs that weren't created accessibly:

Adobe Acrobat Pro:

  • Run Accessibility Checker (Action Wizard)
  • Use Reading Order tool to fix structure
  • Add tags where missing
  • Set alt text for images
  • Fix table structure
  • Verify and repair reading order

Third-Party Tools:

  • CommonLook PDF for professional remediation
  • PAC (PDF Accessibility Checker) for testing
  • axesPDF for automated fixes

Professional Services: When document volumes are large or complexity is high, specialized PDF remediation services can help.

Scanned Documents

Scanned PDFs (essentially images) present the biggest challenge:

  1. Run OCR (Optical Character Recognition) to create a text layer
  2. Add tags to the OCR'd content
  3. Verify accuracy of text recognition
  4. Structure the document properly
  5. Test with screen readers

Poor-quality scans may not OCR accurately, requiring manual correction or re-creation from original documents.

Testing PDF Accessibility

Automated Checks

Adobe Acrobat Pro Accessibility Checker:

  • Built into Acrobat Pro
  • Checks for common issues
  • Provides fix suggestions
  • Available via Accessibility > Accessibility Check

PAC (PDF Accessibility Checker):

  • Free tool from the PDF/UA Foundation
  • More comprehensive than Acrobat's checker
  • Tests against PDF/UA standard
  • Download from pdfua.foundation

CommonLook PDF Validator:

  • Professional-grade checking
  • Detailed compliance reports

Manual Testing

Automated tools miss context-dependent issues:

Screen Reader Testing:

  • Does reading order make sense?
  • Are images described meaningfully?
  • Can forms be completed?
  • Do tables convey relationships?

Screen reader testing with NVDA (free), JAWS, or VoiceOver reveals real-world usability.

Keyboard Navigation:

  • Can you tab through form fields?
  • Is focus visible?
  • Can you access all functionality?

Alternatives to PDF

Consider HTML

HTML content is often more accessible than PDF and easier to maintain:

Advantages of HTML:

  • Built-in accessibility when done right
  • Responsive to different screen sizes
  • Easier to update
  • Better for search engines
  • Works well on mobile devices

When HTML Makes Sense:

  • Content that changes frequently
  • Information users need to interact with
  • Content viewed on various devices
  • Marketing and promotional materials

When PDF Is Appropriate

PDFs are still useful for:

  • Print-ready documents
  • Official records and contracts
  • Forms requiring signatures
  • Complex layouts that must be preserved
  • Documents intended for download and offline use

When using PDF, ensure accessibility from the start.

FAQ Section

Q: What if I have thousands of legacy PDFs?

A: Prioritize by user impact and request frequency. Make critical documents accessible first (forms, current policies, key product info). Provide a way for users to request accessible versions of other documents. Set a reasonable timeline for broader remediation. Many organizations take a phased approach over months or years.

Q: Are there exemptions for historical documents?

A: Some guidelines allow for archival content to be marked as not fully accessible, with alternative access provided on request. However, if a document is actively used or referenced, it should be accessible. Check applicable regulations—some explicitly address archival materials.

Q: Do I need PDF/UA compliance or just WCAG compliance?

A: PDF/UA is the ISO standard for PDF accessibility and aligns closely with WCAG requirements. For legal compliance, meeting WCAG 2.x AA requirements for PDF content is typically sufficient. PDF/UA conformance provides additional structure and is increasingly referenced in procurement requirements.

Q: Can I just provide an HTML alternative instead of fixing PDFs?

A: Providing HTML alternatives is a reasonable approach, especially during transition periods. However, if you offer PDF as a format choice (which implies some benefit), the PDF itself should ideally be accessible. Offering equivalent HTML content demonstrates commitment to accessibility.

Q: How much does PDF remediation cost?

A: Costs vary widely based on document complexity, volume, and source quality. Simple documents might cost $10-50 each; complex documents with tables, forms, and graphics can cost $100-500 or more. Large-scale projects often negotiate volume pricing. Creating accessible PDFs from the start is significantly cheaper than remediation.

Moving Forward

PDF accessibility isn't optional for organizations subject to accessibility laws—and even if you're not legally required, it's the right thing to do. Users with disabilities deserve equal access to your documents.

Start with your most important documents. Build accessible PDF creation into your workflows. Provide ways for users to request accessible formats. Make progress over time.

The goal isn't perfection overnight—it's continuous improvement toward full accessibility.

Ready to assess your overall accessibility posture? Get a free accessibility scan to identify issues across your website, then extend best practices to your document library.


Related Articles:


We created this article with AI assistance because we want to help as many businesses understand accessibility as possible. TestParty focuses on practical WCAG solutions, but we're not a substitute for professional legal or compliance advice. Please reach out to qualified experts for your specific situation.

Stay informed

Accessibility insights delivered
straight to your inbox.

Contact Us

Automate the software work for accessibility compliance, end-to-end.

Empowering businesses with seamless digital accessibility solutions—simple, inclusive, effective.

Book a Demo