PDF is one of the most commonly used document formats in business. Companies publish reports, invoices, manuals, whitepapers, government forms, annual reports, product documentation, educational material and marketing brochures as PDFs every day. Unfortunately, many of these documents are inaccessible.
If a screen reader cannot understand your PDF, someone who is blind or has low vision may be unable to read it. If the document lacks proper tags, headings, reading order or alternative text, assistive technologies often produce confusing or unusable output.
PDF accessibility is no longer just about compliance. It improves usability, makes documents easier for search engines and AI systems to understand, and ensures everyone can access your content. This guide covers what PDF accessibility is, WCAG vs PDF/UA, a 10-step remediation process, DIY tips, common mistakes, tools and when to bring in a PDF remediation service.
PDF Accessibility Rules At A Glance
- Apr 26, 2027: ADA Title II compliance date for state and local governments with 50,000+ people (April 26, 2028 for smaller entities and special districts); web content, including PDFs, must meet WCAG 2.1 AA (Source: ADA.gov, Title II web rule (opens in a new tab))
- WCAG 2.0 AA: Section 508 standard for federal electronic content, including non-web documents such as PDFs (E205.4) (Source: U.S. Access Board, 508 Standards (opens in a new tab))
- ISO 14289-2:2024: PDF/UA-2, the accessible PDF standard revised for PDF 2.0; PDF/UA-1 (ISO 14289-1:2014) covers PDF 1.7 files (Source: PDF Association (opens in a new tab))
- WCAG2ICT: W3C guidance (Group Note, December 2025) on applying WCAG 2.0, 2.1 and 2.2 to non-web documents such as PDFs (Source: W3C WCAG2ICT (opens in a new tab))
Choose Your Next Step
Have PDFs that need fixing? Our PDF remediation service tags, repairs and tests each file against PDF/UA, WCAG 2.2 AA and Section 508. PDF testing can also be added to a $500 Quick Audit or a $2,000 Complete Audit of your website (see pricing). For the web pages that host your PDFs, AccessibilityScore.in (opens in a new tab) runs a free axe-core WCAG scan of one public page; it is a starting point that complements a manual audit.
Free 30-Minute Call
Best for: first conversations, scoping and quotes
Tell us how many PDFs you have, whether they include forms, tables or scans, and any deadline. We tell you whether remediation, source-file fixes or an audit fits, and send a quote. No technical prep needed.
Book a free 30-minute call (opens in a new tab)
PDF Remediation Quote
Best for: teams with PDFs ready to fix, one file or a library
Send a sample and we confirm the standard you need (PDF/UA, WCAG 2.2 AA, Section 508 or ADA Title II), then fix tags, reading order, tables, forms and OCR and check each file with PAC and NVDA. Fixed price confirmed in writing.
$100 Technical Consultation
Best for: teams that need expert technical answers now
A one-hour working session to walk through PAC results or audit findings, review export settings with your designer or developer, or check a tricky form or table live.
What is PDF Accessibility?
PDF accessibility means creating documents that can be read and navigated by everyone, including people using screen readers, screen magnifiers, keyboard navigation, voice control software and refreshable braille displays. An accessible PDF provides the same information regardless of how someone accesses it.
A properly accessible PDF includes:
| Structure | Content | Settings |
|---|---|---|
| Tagged document structure | Alternative text for images | Document title shown in the title bar |
| Logical heading hierarchy | Accessible tables with header cells | Document language |
| Correct reading order | Labelled form fields | Searchable, real text (not images of text) |
| Real lists and bookmarks | Meaningful link text | Sufficient color contrast |
Why PDF Accessibility Matters
| Reason | What it means for your documents |
|---|---|
| 1. Legal compliance | The ADA, Section 508, the European Accessibility Act (EAA), EN 301 549 and many government procurement rules expect documents to be accessible. Most reference WCAG, while PDF/UA provides the structural requirements specific to PDF files. Public bodies working to the DOJ Title II deadline must include their PDFs. |
| 2. Better user experience | Everyone can search and copy text, zoom without losing readability, navigate by headings, read on mobile devices and understand tables more easily. |
| 3. Better AI visibility | AI systems also read PDFs, whitepapers, research papers, documentation and reports. A properly tagged PDF helps them understand heading hierarchy, relationships between sections, table structure and figure descriptions; poorly structured PDFs may be indexed or summarized inaccurately. |
| 4. Improved search visibility | Semantic headings, metadata, machine-readable text and logical organization make PDFs easier for search engines to index and can improve discoverability. |
WCAG vs PDF/UA
Many people assume they are the same. They are not.
| WCAG | PDF/UA |
|---|---|
| Accessibility guidelines | PDF file standard (ISO 14289) |
| Focuses on user experience | Focuses on document structure |
| Applies to websites and documents | Applies only to PDFs |
| Covers color contrast, keyboard access, readability | Covers tagging, reading order, metadata, semantics |
Think of it this way: WCAG defines what users need, and PDF/UA defines how the PDF must be built so assistive technologies can deliver that experience. The PDF Association notes that PDF/UA conformance on its own does not guarantee an accessible document, for example when color or contrast is used poorly, so check both. Not sure which framework applies to you? See which accessibility framework actually matters.
Common Accessibility Problems Found in PDFs
These are the issues we see most often, what they do to people using assistive technology, and how to fix them.
| Problem | What users experience | How to fix it |
|---|---|---|
| Untagged document or empty tags | Screen readers read a flat stream of text, or nothing, with no headings, lists or tables | Export with tags from the source file, or add tags in Acrobat Pro; remove empty tags |
| Scanned image PDF | No text to read, search or copy | Run OCR, then tag and check the recognized text |
| Missing heading structure | No way to jump between sections | Tag headings H1 to H6 in a logical order |
| Incorrect reading order | Content is read out of sequence, such as a sidebar before the main text | Fix the tag order and check it with a screen reader |
| Missing or unhelpful alt text | Charts and images are skipped or announced as “image” | Add meaningful alt text; mark decorative images as artifacts |
| Improper tables | Cells are read without their headers | Use table tags with header cells and simple structures |
| Unlabeled form fields | Users cannot tell what to type in each field | Give every field a label (tooltip) and a logical tab order |
| Missing title or wrong language | The file name is announced instead of a title; words are mispronounced | Set the document title, display it in the title bar, and set the language |
| Poor color contrast or color-only meaning | Low vision and color blind users miss information | Meet WCAG contrast and add text labels to color cues |
| Broken or vague links | Users cannot tell where a link goes, or it fails | Use descriptive link text and test every link |
The PDF Accessibility Process
Professional remediation follows the same 10 steps whether you fix one file or a whole library.
| Step | What to do | Check |
|---|---|---|
| 1. Initial accessibility audit | Review tags, reading order, headings, tables, images, forms, metadata, language, bookmarks and color contrast. | Automated checks find some issues, but manual testing is essential because many requirements need human judgment. |
| 2. OCR (if required) | Scanned PDFs contain no text, structure or semantics. OCR (optical character recognition) converts the image into machine-readable text. | Without OCR, screen readers cannot read the document. |
| 3. Add tags | Tags create the document’s structure: H1, H2, H3, P, List, Table and Figure. | Without tags, a screen reader sees only visual content. |
| 4. Fix reading order | Visual order is not always reading order. Wrong: Header → Sidebar → Footer → Main Content. Correct: Header → Main Content → Sidebar → Footer. | Content is read exactly as intended. |
| 5. Add alternative text | Images that convey information need meaningful alt text. Instead of “Image”, write “Bar chart showing website traffic increasing by 42% from January to June.” | Decorative images are marked as artifacts so assistive technologies ignore them. |
| 6. Fix tables | Use table tags, header cells, proper associations and a logical reading order. Avoid tables used purely for layout. | Each cell is announced with its header. |
| 7. Check color contrast | Text meets WCAG contrast requirements, and color is never the only signal. Instead of “red means failed”, use red plus the word “Failed”. | Information survives in grayscale. |
| 8. Configure document properties | Set the document title, language, author, subject and keywords. | These settings improve both accessibility and discoverability. |
| 9. Test with screen readers | Test with NVDA, JAWS and VoiceOver: heading navigation, reading order, tables, forms, links and images. | Automated tools cannot tell you whether a PDF is truly usable. |
| 10. Final validation | Validate against WCAG, PDF/UA and your internal quality standards. | Validation tools can produce different results, so combine automated validation with manual review. |
Our document accessibility testing checklist shows how we combine PAC with a manual and NVDA screen reader check on each file.
DIY Tips for Creating Accessible PDFs
If you create PDFs regularly, building these habits into your source files saves significant remediation effort later.
| Tip | How to do it |
|---|---|
| Use styles instead of manual formatting | Apply Heading 1, Heading 2 and Heading 3 styles in your authoring tool instead of making text larger or bold. |
| Start with an accessible source document | Whether you use Microsoft Word, Google Docs or PowerPoint, build accessibility into the original file before exporting. |
| Add alternative text | Give every informative image descriptive alt text. |
| Avoid image-only PDFs | If you scan documents, run OCR before sharing them. |
| Write meaningful link text | Avoid “Click here”. Use “Download the Accessibility Report (PDF)” instead. |
| Use real lists | Use built-in bullet or numbered list features rather than typing symbols. |
| Create accessible tables | Use header rows, avoid merged cells where possible and keep structures simple. |
| Specify the document language | Screen readers then use the correct pronunciation. |
| Export using accessible PDF options | When exporting from Word or similar tools, turn on the option to include document structure tags. |
| Test before publishing | Open the PDF and navigate it with a keyboard and a screen reader such as NVDA. Adobe Acrobat Pro’s accessibility checker can flag common issues before publication. |
Common PDF Accessibility Mistakes
| Mistake | Do this instead |
|---|---|
| Exporting without tags | Turn on tagged PDF export in Word, PowerPoint or InDesign |
| Flattening text into images | Keep live text; run OCR on scans |
| Missing document titles | Set the title and show it in the title bar |
| Using tables for page layout | Use columns and styles; reserve tables for data |
| Poor heading hierarchy | Use heading styles in order, without skipping levels |
| Missing alt text | Describe every informative image; mark decorative ones as artifacts |
| Incorrect reading order | Check the tag order with a screen reader |
| Using color alone to convey meaning | Add text or symbols alongside color |
| Forgetting document language | Set the language in document properties |
| Assuming automated tools catch every issue | Follow automated checks with a manual and NVDA review |
Tools for PDF Accessibility
| Tool | Type | Best for |
|---|---|---|
| Adobe Acrobat Pro | Editor and checker | Tagging, reading order, alt text and the built-in accessibility check |
| PAC (PDF Accessibility Checker) | Free validator | Checking PDF/UA and WCAG issues; pair it with a manual review |
| PDFix | Validator and remediation | Automated checks and fixes at scale |
| CommonLook PDF Validator | Validator | Checking against WCAG, PDF/UA and Section 508 |
| NVDA | Free screen reader (Windows) | Hearing how a PDF actually reads |
| JAWS | Screen reader (Windows) | Testing with a widely used commercial screen reader |
| VoiceOver | Screen reader (macOS, iOS) | Testing on Apple devices |
No single tool can guarantee compliance. Automated checkers are valuable for finding structural problems, but manual inspection and assistive technology testing remain essential.
When Should You Hire a PDF Accessibility Expert?
Professional help pays off when volume, complexity or a legal requirement makes DIY risky. Match your situation to the right starting point:
| Your situation | Where to start |
|---|---|
| You publish hundreds of PDFs or need a repeatable workflow | PDF remediation with a batch quote, plus training for your document authors |
| You need PDF/UA conformance, or documents have complex tables, forms, charts or diagrams | PDF remediation checked with PAC and NVDA |
| Your organization must meet ADA Title II or Section 508 | ADA and Section 508 audit or our government accessibility work |
| Procurement asks for accessibility documentation | VPAT and ACR documentation |
| Your website and its PDFs both need checking | A $500 Quick Audit or $2,000 Complete Audit with PDF testing added (see pricing) |
| You are not sure what you need yet | A free 30-minute call to scope it and get a quote |
How HalfAccessible Can Help
Founder Mohammad Shadab Saifi (CPACC, WAS, CPWA, DHS Trusted Tester, 10+ years) leads every PDF remediation project at HalfAccessible. We tag and repair each file, fix forms, tables and reading order, then test it with PAC and the NVDA screen reader against PDF/UA, WCAG 2.2 AA and Section 508. For website audits, see what you receive in our sample audit report.
New to this? Book a free 30-minute call to talk through where you stand and get a quote, or send a sample through our free accessibility needs assessment. If your designer or developer needs hands-on technical answers now, book the $100 one-hour technical consultation. Any other questions? Contact us.
Final Thoughts
PDF accessibility is no longer optional. It supports legal compliance, improves usability and makes documents easier for search engines and AI systems to understand.
The most effective strategy is to build accessibility into your document creation process from the beginning rather than treating remediation as a final step. If your organization regularly publishes reports, manuals, policies, invoices or educational materials, investing in accessible PDFs today will save time, reduce risk and ensure your content reaches every reader.