How to Check PDF Accessibility Online (w/Examples) + FAQs

Yes, you can check PDF accessibility online using free and paid tools that scan your document against federal standards and WCAG 2.1 AA success criteria. The fastest route is to upload your PDF to a web-based checker like PAC 2024, run Adobe Acrobat Pro’s built-in Accessibility Checker, or use Tingtun PDF Checker to flag missing tags, reading order errors, and untagged images within minutes.

The legal backbone comes from Section 508 of the Rehabilitation Act, which requires federal agencies to make electronic documents accessible, and the Department of Justice’s 2024 ADA Title II web rule that binds state and local governments to WCAG 2.1 AA by April 2026 or April 2027, depending on size. Private businesses face exposure under ADA Title III, which courts have applied to digital content in rulings like Robles v. Domino’s Pizza. Ignoring these rules triggers lawsuits, DOJ consent decrees, and in federal procurement, contract disqualification.

According to the WebAIM 2024 PDF Accessibility Report, roughly 77% of PDFs tested on popular websites failed basic automated accessibility checks, showing how widespread the problem remains.

Here is what you will learn in this guide:

• 🧰 Which online checkers work best for Section 508, ADA, and PDF/UA (ISO 14289) conformance
• ⚖️ How federal and state laws apply to PDFs posted online, filed in court, or used in hiring
• 🧪 Step-by-step walkthroughs with named examples from agencies, universities, and law firms
• 🚫 The seven most common mistakes that break screen reader support and how to fix each one
• 📋 A printable pre-publish checklist plus FAQs covering court filings, EEOC forms, and vendor contracts

What “PDF Accessibility” Really Means Under U.S. Law

PDF accessibility means a document works with assistive technology — screen readers, refreshable Braille displays, switch devices, and voice control — so a person with a disability gets the same information as a sighted user. The controlling technical standard for federal agencies is Section 508’s Revised 508 Standards, which incorporate WCAG 2.0 Level AA by reference and adopt PDF/UA where applicable. For state and local governments, the new 28 CFR Part 35, Subpart H raises the bar to WCAG 2.1 AA.

The statute behind federal rules is 29 U.S.C. § 794d, which forces federal agencies to buy, build, and post only accessible electronic content. A violation lets the public file an administrative complaint under Section 508’s enforcement path and, since 1998, the government may block payment on noncompliant vendor deliverables.

A real-world example: when the IRS posts Form 1040 instructions, the PDF must carry logical tags, alt text on charts, and readable tables so a blind taxpayer using JAWS hears the same content a sighted taxpayer reads. The consequence of a tagless IRS PDF is a valid Section 508 complaint and a blocked procurement cycle for the vendor that produced it.

A common misconception is that saving a Word file as PDF makes it accessible. It does not. The source file must contain proper heading styles, alt text, and table headers before export, or the PDF inherits the same barriers.

The Four Legal Frameworks That Drive PDF Testing

Four overlapping frameworks decide whether your PDF passes muster. The first is Section 508, which governs federal agencies and their contractors. The second is the Americans with Disabilities Act, split into Title II (state and local governments, public universities, courts) and Title III (private businesses open to the public).

The third is Section 504 of the Rehabilitation Act, which reaches any program receiving federal funds, including most hospitals, K-12 schools, and nonprofits. The fourth is the 21st Century Communications and Video Accessibility Act (CVAA), which bites when PDFs embed video captions or audio instructions.

The consequence of ignoring any of these is stacked liability. A state university hospital can be sued under Title II for its patient portal and under Section 504 for the same PDF intake form. Both awards can include attorneys’ fees under 42 U.S.C. § 12205.

The Core Technical Standards: WCAG 2.1 AA and PDF/UA

WCAG 2.1 Level AA sets 50 success criteria across four principles: perceivable, operable, understandable, and robust. For PDFs, the five criteria that fail most often are 1.1.1 Non-text Content, 1.3.1 Info and Relationships, 1.4.3 Contrast (Minimum), 2.4.6 Headings and Labels, and 4.1.2 Name, Role, Value.

PDF/UA (ISO 14289-1) is the only ISO standard written specifically for PDFs. It adds rules WCAG cannot fully enforce, such as a properly declared document language, real tags (not artifacts), and a logical reading order embedded in the structure tree. The PDF Association’s Matterhorn Protocol 1.1 lists 136 failure conditions that checkers use as a shared rulebook.

A plain-English way to think about it: WCAG tells you what must be accessible; PDF/UA tells you how a PDF must encode it. The consequence of failing one but passing the other is a document that works in Acrobat but breaks in NVDA or on a mobile screen reader.

Success Criterion 1.1.1 — Non-text Content

Every image, chart, icon, and scanned page must carry alt text or be marked as decorative. The rule comes from WCAG 2.1 SC 1.1.1, and PDF/UA reinforces it through the /Alt entry on figure tags.

The consequence of a missing alt attribute is silence — a screen reader skips the image entirely, so a blind user never learns that a W-2 form contains a signature block or that a medical PDF shows a dosage chart.

Example: Maria, a paralegal at a Vilnius-based firm’s U.S. office, exports a deposition exhibit with 12 photos. Without alt text, opposing counsel’s blind attorney cannot review the exhibits, which can trigger a Rule 34 discovery dispute and sanctions.

A common misconception is that alt text must describe every pixel. It should describe the purpose of the image in context, not its artistic details.

Success Criterion 1.3.1 — Info and Relationships

SC 1.3.1 requires that visual structure — headings, lists, tables, columns — be encoded in tags a machine can read. Visual bolding alone does not create a heading.

The consequence of skipping real tags is catastrophic: a 200-page federal rulemaking PDF becomes one long run-on paragraph to a screen reader user.

Example: The Federal Register tags every proposed rule so advocates using VoiceOver can jump heading by heading. A private law firm that files an amicus brief without tags loses the same navigability and may violate local court e-filing rules.

Top Online PDF Accessibility Checkers (2026)

You have five reliable online or desktop-online hybrid checkers to pick from, each with a different strength. The table below compares them on cost, standards coverage, and best use case.

How PAC 2024 Works, Step by Step

PAC 2024 is published by the PDF/UA Foundation and is the closest thing the industry has to a neutral reference checker. You download the Windows app, drag your PDF into the window, and PAC runs all 136 Matterhorn checks plus WCAG mapping.

The report shows pass, warning, and fail icons beside each rule, plus a “Screenreader Preview” that renders the tag tree the way JAWS would read it. The consequence of ignoring a PAC failure is that your document will still look fine visually but will fail a federal Trusted Tester review.

Example: Darius, a state agency webmaster in Illinois, runs PAC on a budget PDF and finds 14 untagged tables. He fixes them in Acrobat, re-runs PAC, and gets a clean report before posting — avoiding a DOJ Title II investigation now that the 2024 web rule has teeth.

How Adobe Acrobat Pro’s Checker Works

Open the PDF in Adobe Acrobat Pro, choose All Tools → Prepare for Accessibility → Check for Accessibility, pick the categories you want, and click Start Checking. Acrobat returns a tree with 32 rules grouped under Document, Page Content, Forms, Alternate Text, Tables, and Lists.

The tool has real limits. It cannot judge whether alt text is meaningful, whether reading order makes sense, or whether color contrast meets 4.5:1 on gradients. That is why Adobe flags “Logical Reading Order” and “Color Contrast” as manual checks you must confirm by eye or with a contrast analyzer.

The consequence of relying only on Acrobat’s green checkmarks is a false sense of security; WebAIM’s 2024 survey found that 40% of PDFs that passed Acrobat still failed manual review.

Step-by-Step: Testing a PDF Online in 10 Minutes

The fastest workflow blends two tools. First, run the file through Acrobat’s built-in checker to catch the obvious misses. Second, upload the same file to PAC 2024 for the deep Matterhorn audit. Third, open the PDF in a free screen reader like NVDA and listen to the first three pages.

Step one: export your source file (Word, InDesign, Google Docs) with “Document structure tags for accessibility” turned on in the Save-As dialog. Step two: add document properties — title, author, language — through File → Properties → Description. Step three: run the Acrobat checker, fix every Fail, then manually verify reading order using the Reading Order tool.

Step four: upload to PAC 2024 and resolve any Matterhorn failures. Step five: test with NVDA by pressing Insert+Down Arrow to hear continuous reading; listen for skipped images, misread tables, and wrong pronunciation caused by missing language tags.

A common mistake is stopping after step three. The consequence is a PDF that passes Acrobat but still fails a DOJ audit, because Acrobat does not test PDF/UA syntax.

Three Realistic Scenarios and Their Outcomes

The table below maps three common situations to the outcome a user will experience if the PDF is not fixed before posting.

Named Examples From Three Industries

Meet Jamal, a contracting officer at the General Services Administration. He reviews a vendor’s Section 508 Accessibility Conformance Report before awarding a $4 million task order. When the vendor’s sample PDF fails PAC, Jamal rejects the deliverable under FAR 39.204, saving the agency a later lawsuit.

Meet Priya, an accessibility coordinator at a large state university. She scans every faculty syllabus PDF each semester with Grackle and emails instructors a remediation list. Because her state adopted the 2024 DOJ Title II rule on the earlier April 2026 deadline, missing the fix means institutional liability, not just individual embarrassment.

Meet Robert, a civil rights attorney filing a class action complaint in the Southern District of New York. He runs his 80-page exhibit packet through PAC and Acrobat before CM-ECF upload so blind co-counsel and any blind juror can read it. A failure here can trigger a Local Rule 5.2 technical-filing objection.

Key Court Rulings That Shape PDF Accessibility

Courts increasingly treat inaccessible PDFs as ADA violations. In Robles v. Domino’s Pizza, LLC, 913 F.3d 898 (9th Cir. 2019), the Ninth Circuit held that Title III applies to websites and apps tied to physical stores, a rule lower courts now extend to hosted PDFs. The Supreme Court denied certiorari, letting the ruling stand.

In National Federation of the Blind v. Target Corp., 452 F. Supp. 2d 946 (N.D. Cal. 2006), the court allowed a Title III claim over an inaccessible website, setting the template for document-level accessibility suits. The consequence for Target was a $6 million settlement plus ongoing monitoring costs.

More recently, the DOJ settlement with H&R Block required the company to bring its online tax forms — including exportable PDFs — to WCAG 2.0 AA. A common misconception is that settlements do not bind other companies; while technically true, they telegraph DOJ’s enforcement priorities and are cited in demand letters every week.

The 2024 DOJ Title II Rule in Plain English

The rule at 28 CFR § 35.200 requires state and local governments to make web content and mobile apps conform to WCAG 2.1 AA. Large public entities (population of 50,000 or more) had to comply by April 24, 2026; smaller entities have until April 26, 2027.

The consequence of noncompliance is direct DOJ enforcement under Title II, private lawsuits, and loss of federal grant funds that flow through Section 504 assurance agreements.

Example: A county clerk posts marriage license PDFs that are scanned images with no OCR. After April 2026, that county is on the clock and a single complaint can open a systemic investigation.

Mistakes to Avoid When Checking PDFs

Automated checkers are only a floor. The following mistakes are the seven most common reasons PDFs still fail real-world audits after an automated “pass.”

• Skipping manual reading-order review. Automated tools cannot tell that a sidebar was read before the main column. The outcome is a screen reader that speaks nonsense paragraphs to users.
• Treating scanned pages as text. A PDF of a scanned contract is an image. Without OCR, screen readers read nothing, and a litigant can move to strike under FRE 1002.
• Forgetting to set document language. Missing the /Lang entry makes screen readers mispronounce words. A Spanish medical consent form read in English pronunciation can rise to an informed consent defect.
• Using color alone for meaning. Red “required” asterisks without a text label break WCAG 1.4.1. The outcome is a colorblind applicant submitting an incomplete form.
• Ignoring form field labels. Unlabeled PDF form fields are the top federal-procurement failure. The outcome is a tax form the user cannot complete without sighted help, defeating privacy.
• Relying only on Acrobat’s checker. As noted, Acrobat misses PDF/UA syntax errors. The outcome is a document that passes Acrobat but fails PAC and a Trusted Tester review.
• Not testing with a real screen reader. Five minutes in NVDA catches what automation misses every time. Skipping this step is the single biggest predictor of a later complaint.

Seven More Advanced Pitfalls

Beyond the basics, experienced remediators watch for seven advanced traps. The first is nested tables, which screen readers often flatten into gibberish. The second is artifacting real content — marking a heading as decorative removes it from the tag tree entirely.

The third is using auto-tagging on complex layouts; auto-tag is a starting point, not a finish line. The fourth is inconsistent heading levels — jumping from H1 to H4 breaks navigation for users of JAWS list-of-headings.

The fifth is decorative images that still carry alt text, forcing users to hear meaningless descriptions. The sixth is linked cross-references without descriptive text — “click here” tells a blind user nothing. The seventh is encrypted PDFs that block assistive tech; set the “Enable text access for screen reader devices for the visually impaired” flag in Acrobat’s Security settings.

Do’s and Don’ts for PDF Accessibility

The short list below separates habits that protect you from habits that invite lawsuits.

Do’s

• Do start accessible in the source file, because fixing Word is ten times cheaper than fixing PDF, per WebAIM cost studies
• Do set document title, author, and language in File → Properties, because screen readers announce these first
• Do add alt text to every figure, because SC 1.1.1 is the most-cited failure in DOJ letters
• Do test with NVDA or VoiceOver, because WebAIM 2024 shows automation catches only 60% of real issues
• Do keep an Accessibility Conformance Report on file, because federal buyers require it before award

Don’ts

• Don’t rely on auto-tagging alone, because it regularly mislabels tables and columns
• Don’t scan paper and post it, because a scanned PDF is invisible to screen readers without OCR
• Don’t password-protect without enabling assistive-tech access, because 17 U.S.C. § 1201(d) exceptions do not excuse ADA violations
• Don’t use color as the only cue, because WCAG 1.4.1 bans it and colorblind users miss the signal
• Don’t skip form field labels, because unlabeled fields are the top Section 508 procurement fail

Pros and Cons of Online PDF Accessibility Checkers

The tools save time but carry trade-offs. The lists below capture the main ones.

Pros

• Fast feedback, because most checkers return results in under a minute
• Standardized rules, because Matterhorn Protocol gives a shared scoring system
• Free options exist, because PAC 2024 and Tingtun cost nothing
• Integration with workflows, because Acrobat and Grackle plug into Adobe and Google pipelines
• Audit-ready reports, because PDF and HTML exports support procurement and legal review

Cons

• False confidence, because a green score does not guarantee real accessibility
• Limited semantic review, because tools cannot judge meaningful alt text
• Upload privacy risk, because cloud checkers may store sensitive PDFs; review the tool’s privacy policy before upload
• Desktop-only for deep checks, because PAC 2024 requires Windows
• License cost for enterprise tools, because CommonLook and axesPDF run into the thousands annually

PDF Forms, Court Filings, and Federal Procurement

PDF forms deserve their own spotlight because they carry the highest legal exposure. The EEOC charge form and the IRS W-4 are both interactive PDFs; if either is untagged, the agency faces a Section 508 complaint and a Title II or Section 504 claim.

Court filings add a second layer. The PACER/CM-ECF system does not enforce tagging at upload, but many district courts have local rules — for example, the Northern District of California’s ECF Procedures — that require searchable, OCR’d filings. An untagged exhibit can be rejected or stricken, costing billable hours and missed deadlines.

Federal procurement closes the loop. Under FAR Part 39 and the Revised 508 Standards, agencies must require an Accessibility Conformance Report from every vendor supplying electronic documents. The consequence of skipping the ACR is a contract challenge under GAO bid protest rules and, in some cases, False Claims Act exposure under 31 U.S.C. § 3729.

The Accessibility Conformance Report (ACR) in Detail

The ACR template — still widely called a VPAT — walks you through each WCAG and 508 criterion with columns for “Conformance Level” (Supports, Partially Supports, Does Not Support, Not Applicable) and “Remarks and Explanations.” Vendors must complete every row honestly.

A common misconception is that “Partially Supports” hides gaps. It does the opposite: any “Does Not Support” or “Partially Supports” entry is a red flag a federal buyer will push back on. The consequence of overstating conformance is a False Claims Act risk; the DOJ has used 31 U.S.C. § 3729 against IT vendors who misrepresented 508 conformance.

Example: A contractor tells the Department of Veterans Affairs its training PDFs “fully support” WCAG 2.0 AA. An internal VA Trusted Tester finds 14 failures. The VA can claw back payment and refer the matter for FCA investigation.

The Trusted Tester Program

The DHS Trusted Tester v5 program certifies federal reviewers in a uniform testing methodology. Many agencies require vendor deliverables to pass a Trusted Tester review, and the methodology is published and free.

The consequence of skipping Trusted Tester testing is that your “green” Acrobat report may still fail the government’s own process, costing you the contract. Darius from the Illinois agency example earlier chose Trusted Tester-trained staff specifically to avoid that outcome.

A common misconception is that Trusted Tester is only for federal use. Nothing stops a private law firm, hospital, or university from adopting the same protocol, and doing so strengthens any future defense to an ADA claim.

Your Pre-Publish PDF Accessibility Checklist

Run this nine-step list before every PDF goes live. Each step ties to a rule or standard you can point to in a dispute.

1. Set document Title, Author, Language, Subject under File → Properties.
2. Confirm every image has meaningful alt text per WCAG 1.1.1.
3. Verify heading levels are sequential (H1 → H2 → H3) using Acrobat’s Tag panel.
4. Label every form field and group related fields with fieldsets.
5. Tag tables with header rows and scope attributes.
6. Check color contrast at 4.5:1 for text and 3:1 for large text via a contrast analyzer.
7. Confirm reading order with Acrobat’s Reading Order tool.
8. Run PAC 2024 and resolve every Matterhorn failure.
9. Listen to at least the first three pages in NVDA or VoiceOver.

State Nuances You Cannot Ignore

Federal law sets the floor, but several states go further. California’s Unruh Civil Rights Act allows $4,000 per violation and has fueled thousands of web-accessibility suits. New York State Technology Law § 103 requires state agency content to meet accessibility rules issued by the state CIO.

Colorado HB 21-1110 requires state and local government digital content to meet accessibility standards, with a private right of action beginning July 1, 2024. Texas Government Code § 2054.453 mirrors Section 508 for state agencies. The consequence of treating federal compliance as enough is statutory damages in California and Colorado, and administrative penalties in New York and Texas.

A common misconception is that an out-of-state business is safe. California courts have applied the Unruh Act to non-California businesses whose websites serve California users, per cases like Thurston v. Midvale Corp..

FAQs

Is a PDF automatically accessible if it passes Adobe Acrobat’s checker?

No. Acrobat flags only 32 rules and skips PDF/UA syntax. Run PAC 2024 and a live screen-reader test before trusting any green checkmark.

Do I have to make every PDF on my site accessible under the ADA?

Yes. ADA Title II and Title III both reach hosted PDFs; exceptions exist only for archived pre-compliance-date documents that are not currently used.

Can I be sued personally if my employer’s PDFs are inaccessible?

No. ADA suits target the entity, not employees; however, officers of small LLCs can face personal exposure under state civil rights laws like California’s Unruh Act.

Does Section 508 apply to private companies?

Yes. It applies whenever a private company sells electronic content to a federal agency, via FAR Part 39 flow-down clauses and ACR requirements.

Is OCR enough to make a scanned PDF accessible?

No. OCR creates searchable text, but you still need tags, alt text, headings, and reading order before the PDF meets WCAG 2.1 AA or PDF/UA.

Do court filings have to be accessible?

Yes. Many district courts require OCR’d, searchable filings, and ADA Title II reaches state courts directly; federal courts follow internal accessibility policies enforced by the Administrative Office.

Does the 2024 DOJ Title II rule cover PDFs?

Yes. 28 CFR § 35.200 applies WCAG 2.1 AA to web content and mobile apps, which the rule’s preamble explicitly includes PDFs within.

Can I use a free online checker for HIPAA-protected PDFs?

No. Most free cloud checkers store uploaded files; use a desktop tool like PAC 2024 to keep PHI under your control.

Is PDF/UA the same as WCAG?

No. PDF/UA is a technical PDF standard; WCAG 2.1 is a content standard. You generally need both to satisfy U.S. legal requirements.

Does Section 504 reach PDFs at a private hospital?

Yes. Any entity that accepts Medicare or Medicaid funding is bound by Section 504, which OCR enforces through complaint investigations and fund-withholding.

Can auto-tagging in Word produce a fully accessible PDF?

No. Auto-tagging is a helpful start, but every complex document needs manual review for reading order, meaningful alt text, and table structure before export.

Are accessibility overlays on PDFs legal shields?

No. DOJ and federal courts have rejected overlay defenses; rulings like Murphy v. Eyebobs confirm that overlays do not cure underlying accessibility failures.