Skip to main content

ADA Title II|WCAG 2.1 AA required by April 26, 2027 (50,000+) and April 26, 2028 (smaller entities, special districts)

Free tool · runs in your browser

PDF accessibility checker

Drop in an agenda, budget, form or newsletter. The file is read in your browser, never uploaded, and checked for the most common PDF accessibility failures.

Results

Choose a file to start.

What this checker tests

CheckWhy it mattersReference
Tagged PDFTags give screen readers headings, lists, tables and reading order.PDF/UA 7.1, WCAG 1.3.1
Document languageSets correct pronunciation for speech output.WCAG 3.1.1
Title and "display title"People hear a meaningful title, not "agenda_final_v3.pdf".WCAG 2.4.2
Real textScanned pages are pictures of text; nothing can be read aloud or searched.WCAG 1.1.1, 1.4.5
Figure alt textCharts, maps and photos need a text alternative.WCAG 1.1.1
Form field namesFillable fields must announce what to type.WCAG 1.3.1, 4.1.2
Bookmarks (long files)Lets people jump to a section of a long budget or plan.WCAG 2.4.5
Security settingsRestrictions must not block assistive technology.PDF/UA 7.16

What it cannot test

Whether the reading order is logical, whether headings are nested correctly, whether table header cells are marked, whether alt text actually describes the image, and color contrast. Use the free PAC checker or Acrobat Pro's Accessibility Check for a full PDF/UA review, and listen to the document with a screen reader.

A publishing habit that prevents most PDF problems

  1. Publish information as a web page whenever you can. HTML is easier to make accessible and easier to read on a phone.
  2. When a PDF is necessary, build it from a properly structured Word or Google Docs file: real heading styles, alt text on images, a header row on tables.
  3. Run the built-in accessibility checker in Word before exporting, and export with tags.
  4. Never post a scan of a printed page as the only version.

Read our full guide to accessible PDFs for public entities for what the ADA Title II rule says about documents.

Sources

  1. eCFR, 28 CFR Part 35 Subpart H
  2. W3C, PDF Techniques for WCAG 2.1
  3. PDF Association, PDF/UA in a nutshell
  4. Mozilla pdf.js

Questions

Frequently asked

Is my PDF uploaded anywhere?

No. The checker uses the open-source pdf.js library inside your browser tab. The file never leaves your computer, so it is safe for drafts and internal documents.

Does passing these checks make a PDF accessible?

No. These are machine checks for structural problems. A person still needs to review reading order, heading levels, table headers, the quality of alt text and color contrast, ideally with a screen reader or a dedicated tool such as PAC or Acrobat Pro's full check.

Do old PDFs on our site have to be fixed under ADA Title II?

The DOJ rule exempts preexisting conventional electronic documents posted before your compliance date, unless they are currently used to apply for, access or participate in your services. New documents and documents people still use, such as current forms, are covered. See our PDF accessibility guide for details.

What does tagged PDF mean?

Tags are a hidden structure layer that labels headings, paragraphs, lists, tables and images and sets the reading order. Without tags, a screen reader reads whatever order the text happens to be stored in.

What is the fastest way to fix a failing PDF?

Fix the source file. In Word or Google Docs use real headings, alt text and table headers, then export with tagging turned on. For scanned paper, run OCR and tag the result, or publish the content as a web page instead.