ADA PDF Remediation Checklist: Before Your Deadline Passes

Crawl every public-facing domain and subdomain

Use a web crawler to extract all PDF URLs across every domain, subdomain, and embedded content management system your agency operates. Include legacy subdomains that may not appear in your main navigation. A 200-page website can host thousands of PDFs in directories nobody actively manages.

Check your CMS document libraries and asset managers

CMS document libraries frequently contain PDFs that are not linked from any visible page but are still publicly accessible by direct URL. These are still covered by the rule. Export a full asset list from your CMS to cross-reference with crawler results.

Identify all third-party hosted PDFs you control

PDFs hosted on SharePoint, Google Drive, Dropbox, or third-party platforms but linked from your government website are covered if your agency controls them. Build a complete list of externally hosted documents linked from your pages.

Catalogue by publication date

Documents published after June 24, 2024 require immediate compliance. Documents published before that date require compliance by your deadline. Knowing the publication dates for your archive determines which documents are in immediate violation versus those on a remediation timeline.

Record file size, page count, and format for each document

Remediation effort is largely driven by page count and whether the PDF is a tagged document, a scanned image, or a mixed document. A 2-page council agenda takes 10 minutes to tag. A 200-page environmental impact report takes hours. Capture this metadata during inventory, it drives your prioritisation.

Identify PDF creators and owners

PDFs are usually owned by specific departments: legal, planning, HR, finance. Knowing who created each document tells you who can supply the source file. Remediation from source files is 70% faster than remediating PDFs with no source. Map documents to departments during inventory.

Flag documents that may have legal or archival protection

Some government documents, signed contracts, court records, historical archives, have special handling requirements. Identify these before starting remediation so you don't accidentally alter protected records. For scanned historical documents, accessible HTML alternatives are often the right answer rather than touching the PDF.

Run PDF/UA automated checks on the full archive

Tools like PAC 3, Adobe Accessibility Checker, or Keyspider's AI PDF Audit Tool can process thousands of PDFs in batch. The output should include a per-document pass/fail score and a breakdown of failure categories: missing tags, missing alt text, untagged tables, no document language set, missing title metadata, poor reading order.

Identify and separately flag scanned image PDFs

Scanned PDFs with no machine-readable text fail virtually every accessibility check and require OCR plus full tagging. They need a different remediation workflow than native PDFs with structural failures. Flag them as a separate category with their own priority queue.

Check for missing document language attribute

Every PDF must have the document language set in its properties. Missing language declarations are one of the most common failures and one of the easiest to fix at scale. Screen readers cannot correctly pronounce content when the language is unset, a failure that affects every user of assistive technology.

Audit heading structure and reading order

Automated tools can flag absent heading structure and reading order anomalies. A PDF where the reading order jumps from page header to page footer before reaching the main content is inaccessible to screen reader users even if it visually appears correct. Flag all documents where reading order fails automated checks.

Check colour contrast in all documents

Text with insufficient contrast fails WCAG 1.4.3 and is an ADA Title II violation. This particularly affects documents with grey text on white backgrounds, light watermarks behind text, or coloured callout boxes. Automated contrast checking can flag these across the archive in one pass.

Produce a severity-scored inventory list

The audit output should be a spreadsheet: document URL, publication date, page count, failure categories, automated severity score (high/medium/low). This becomes the master remediation queue. Every subsequent phase references it.

Manually audit a 5% sample weighted toward high-traffic documents

Manual audit every document in the top 20% by download volume. For the rest, audit a random 2-3% sample per document category. The sample gives you a realistic picture of failure types that automated tools missed, particularly in reading order, form field accessibility, and table structure.

Test keyboard navigation in all PDF forms

If your archive includes fillable PDF forms, every form field must be keyboard-operable, labelled, and announced correctly by screen readers. Form failures are among the most impactful accessibility barriers because they block residents from completing applications and transactions. Test every distinct form template in your archive.

Verify alt text quality, not just presence

Automated tools check whether alt text exists. They cannot check whether it is accurate or useful. An image tagged with alt text that reads 'image' or repeats the file name fails WCAG 1.1.1. Manual review of all images in your highest-traffic documents is required to catch this.

Check table structure in complex documents

Multi-column tables, tables with merged cells, and tables used for layout rather than data are common sources of screen reader confusion. Manual testing with a screen reader is the only reliable way to verify that tables are announced correctly and that header associations are preserved.

Test with at least two screen readers

NVDA with Firefox and JAWS with Chrome cover the majority of assistive technology users on Windows. VoiceOver with Safari covers Mac and iOS users. Failures that are subtle in one screen reader are often catastrophic in another. Use both for your manual audit sample.

Tier 1: Any document required to access government services

Applications, forms, eligibility documents, benefits guides, permit processes. A resident cannot receive the service if they cannot read the document. These go first, regardless of publication date or page count.

Tier 2: High-traffic informational documents

Use your web analytics to identify the most-downloaded PDFs in the last 12 months. Documents downloaded more than 500 times per month are reaching significant populations. Fix these before addressing low-traffic archival material.

Tier 3: Documents for which source files are available

If you have the original Word, InDesign, or PowerPoint source file, remediation from source takes a fraction of the time of remediating the PDF directly. Batch all documents with available source files into an accelerated track.

Tier 4: Recently published documents

Documents published after June 24, 2024 have no grace period. Even at low traffic volumes, these are in immediate violation. Prioritise any post-June 2024 publication that hasn't been remediated.

Tier 5: Archival and historical content

Documents that are archived, not actively used, and not modified after your compliance date may qualify for the archival exception. Consult your legal team to confirm which documents qualify. Don't invest remediation effort in genuinely exempt documents.

Build a public-facing remediation timeline

Document your tiers, your timeline, and your progress. This is not just good project management. A credible, public-facing remediation plan reduces your DOJ complaint risk significantly. It demonstrates good-faith effort even when full compliance isn't yet achieved.

Remediate from source files wherever possible

Open the original Word or PowerPoint file, apply correct heading styles, add alt text to images, properly structure tables, and export with accessibility settings enabled. Verify the output with PAC 3 or equivalent. This workflow produces the most reliable results and is the fastest path for documents where source files exist.

For PDFs without source files: use AI-assisted tagging

AI remediation tools can analyse document structure, infer heading hierarchy from visual formatting, generate contextually accurate alt text, and reconstruct reading order. For large archives of scanned or untagged PDFs, AI-assisted remediation is the only operationally viable approach.

Review AI-generated alt text for all images

AI-generated alt text is far better than no alt text, but it requires human review for images that carry specific meaning: charts with precise data, maps with location information, diagrams with labelled components. Build a review step for AI-generated alt text on documents where image accuracy matters.

Validate every remediated PDF before publishing

Run every remediated document through PAC 3 automated validation before returning it to the website. Automated validation catches tagging errors introduced during remediation. A remediation that introduces new errors is worse than no remediation: it creates a false sense of compliance.

Spot-check with a screen reader after automated validation

For Tier 1 and Tier 2 documents, supplement automated validation with a 5-minute screen reader check. Navigate through the document using only keyboard and screen reader. The heading structure should be logical, all images announced with descriptive text, all tables navigable by row and column.

Replace non-remediable documents with accessible HTML alternatives

Some documents, particularly complex scanned images of historical material, cannot be practically remediated as PDFs. An accessible HTML page that presents the same information is an acceptable alternative under the rule. Identify these during the audit phase and budget for HTML page creation.

Maintain a remediation log for every document

For each remediated document: original failure categories, remediation method (source file, AI-assisted, HTML replacement), remediation date, validator used, and validation result. This log is your proof of due diligence.

Publish an accessibility statement

Your agency's website should have a publicly accessible accessibility statement that: identifies your conformance target (WCAG 2.1 AA), lists any known exceptions, documents your remediation timeline, and provides a contact mechanism for users who encounter barriers. This is DOJ-expected practice.

Establish a complaint and feedback mechanism

Provide a clearly labelled 'Report an Accessibility Issue' link on every page that contains PDFs. Route these to a named person who can respond within 5 business days. Document every complaint received and the resolution action taken.

Schedule periodic re-audits

Accessibility is not a one-time project. Every time a new PDF is published, it must meet the standard. Build an audit step into your document publishing workflow. Schedule a full re-audit of your archive every 12 months to catch regressions.

Confirm third-party vendor accessibility commitments

If your PDFs are generated by a third-party CMS, form tool, or document management system, confirm in writing that the system outputs accessible PDFs. Vendor-generated non-compliant documents are still your agency's legal responsibility under Title II.