PDF Accessibility for Universities: A Practical Guide

Universities run on PDFs. Course catalogs, syllabi, degree plans, financial-aid forms, faculty-senate minutes, scanned journal articles in the LMS, twenty years of departmental newsletters — a single public university can easily host tens of thousands of them. For a blind student using a screen reader, an untagged PDF is a locked door: the software either reads nothing, or reads the page in an order no human would.

For public institutions, this is no longer just a values question. The DOJ’s ADA Title II rule sets WCAG 2.1 Level AA as the technical standard for public entities’ web content — explicitly including documents posted on it — with compliance deadlines of April 26, 2027 for entities with a population of 50,000 or more and April 26, 2028 for smaller entities, as extended by the April 2026 interim final rule. Public colleges and universities are Title II entities. The PDF backlog is, for most campuses, the single largest gap between where they are and where that rule requires them to be.

The good news: this is a solvable operations problem. Here is the playbook.

Step 1: Find your PDFs — all of them

Nobody knows how many PDFs their institution hosts, and the first count is always a shock. Inventory from three directions:

• Crawl your public web presence— the main domain and every departmental subdomain — and log every linked PDF with its URL and location.
• Export from your systems of record: the CMS media library, the document repositories, the registrar’s and financial-aid offices’ form libraries.
• Sample the LMS. Course shells are typically behind login but are still content you provide to students; scanned readings uploaded by faculty are usually the worst documents on campus.

Capture rough metadata as you go: last-modified date, download traffic if you have it, and owning department. You will need all three for triage.

Step 2: Triage — because you will not fix everything

A backlog of tens of thousands of documents cannot be remediated uniformly, and the rule does not require you to. Sort the inventory into tiers:

• Tier 1 — forms and documents currently used to apply for or access services. Admissions and financial-aid forms, registration documents, housing applications, the current catalog. Highest legal exposure, highest student impact. Fix first.
• Tier 2 — high-traffic informational documents. Degree plans, advising guides, policy handbooks, anything in your top few hundred downloads.
• Tier 3 — the long tail. Old newsletters, past-year event flyers, superseded catalogs.

For Tier 3, the rule’s limited exceptions may help: content that meets the rule’s definition of archived web content, and pre-existing conventional electronic documents that are notcurrently used to apply for or access your services, can qualify for exceptions. Two cautions: the definitions are narrow — a “pre-existing” form students still submit does not qualify — and an exception to the web rule never eliminates your underlying ADA obligation to provide access when someone needs that content. Document exception decisions in writing and review them with counsel.

Step 3: For each document, pick one of four moves

• Retire it.The cheapest remediation is deletion. A meaningful share of any university’s PDFs are obsolete duplicates nobody would miss. Take them down or move them into a properly designated archive.
• Replace it with a web page.If the PDF exists only because someone exported a Word document, the content usually belongs in HTML — which is easier to make accessible, easier to keep accessible, and better on phones.
• Convert it to accessible HTML. For large document sets where manual rework is unaffordable, automated conversion is the scalable path. TheAccessiblePDFconverts PDFs — including scanned ones — into accessible HTML with proper structure, reading order, and alt text, at a per-document cost that makes Tier 2 and Tier 3 backlogs tractable.
• Remediate the PDF itself.Right for documents that must remain PDFs — official forms, documents with signature requirements, precise print layouts. This is skilled manual work; budget accordingly and reserve it for documents that earn it.

Step 4: Know what an accessible PDF actually requires

If a document stays a PDF, “accessible” means, concretely:

• Real text, not pictures of text.Scanned pages must be OCR’d; a screen reader cannot read an image of a paragraph.
• A tag structure with a logical reading order— headings tagged as headings, lists as lists, so assistive technology can navigate rather than just recite.
• Alt text on meaningful images, charts, and diagrams; decorative images marked as artifacts.
• Table header cells marked as headers, so data cells announce their context.
• Labeled form fields with a sensible tab order, for fillable forms.
• A document title and languageset in the file’s properties, plus bookmarks for long documents.
• Sufficient color contrast, and no information conveyed by color alone.

Print this list and hand it to anyone who claims a document is “already accessible” because it opens in a browser.

Step 5: Fix the pipeline, or the backlog grows back

Campuses that remediate the backlog without changing how documents get made are back where they started within a few years. The upstream fixes cost little:

• Accessible source files first. A Word or PowerPoint file built with real heading styles, alt text, and marked table headers exports to a largely accessible PDF. Provide departmental templates that have this built in.
• Train the people who publish.Not everyone — the department admins, communications staff, and web editors who actually post documents. An hour of training on styles and export settings prevents hundreds of future failures.
• Give faculty a better path than the scanner. Library-mediated e-reserves and OCR-on-upload workflows beat asking every instructor to become a remediation expert.
• Put accessibility in procurement. Catalog software, form platforms, and the LMS all generate documents; require WCAG 2.1 AA conformance and an Accessibility Conformance Report from those vendors before signing.

Step 6: Monitor continuously

New PDFs appear on a university website every single day, and a one-time cleanup decays immediately without measurement. Schedule a recurring automated scan of your web presence — a crawler like TheAccessibleAuditcan flag both page-level WCAG failures and newly posted documents — and report the trend line to leadership each quarter. The metric that matters is not “how many PDFs did we fix” but “is the number of inaccessible documents going down while new content stays clean.”

The bottom line

The PDF backlog looks unbounded until you count it, triage it, and stop treating every document as equally worth saving. Retire ruthlessly, convert at scale, hand-remediate only what earns it, and fix the publishing pipeline so the problem stays solved.