Document Inventory and Triage at Institutional Scale

Jeff Fryer
document remediationhigher education accessibilityaccessibility triagecourse materialssection 504

Trust note

This article was written by a person and reviewed against accessibility.chat editorial standards. Treat it as research and education rather than legal advice. We prioritize primary sources and correct material errors.

Alphabet blocks spelling 'EDUCATION' on orange background with pencils.
Photo by Atlantic Ambience on Pexels

You will never remediate everything here. A defensible queue is the difference between a program and a pile.

No sector in this series faces the document volume higher ed does — course materials, scanned readings, library databases, research portals, years of accumulated content across every department. The two-gate approach still applies. It just matters more here, because the alternative to triage isn't a smaller backlog. It's paralysis.

Gate one: should this even be a document?

Retire what's superseded or unopened in years — a common state for course readings from sections that no longer run. Replace with an actual web page whatever never needed to be a PDF. Recreate from the source file wherever it exists; remediating a scanned reading by hand is always more expensive than re-exporting from the original. This gate alone clears a meaningful share of a typical institutional estate before a dollar gets spent, and the decisions are permanent.

Gate two: does an exception actually apply?

The federal rule's exceptions (opens in new window) cover archived content and certain preexisting documents. Test them item by item, in writing, with a named decision-maker. And hold the line on the trap specific to this sector: course content behind an LMS login is not exempt because it's password-protected. That exception covers individualized documents about one specific person, not the readings every enrolled student needs.

Rank by enrollment and reuse, not just traffic

Rank survivors by traffic, stakes, and complaint volume divided by effort — and in this sector, weight legacy scans specifically by enrollment and reuse. A core text assigned every semester in a required course outranks a reading from a seminar that ran once three years ago, even if raw page-view traffic doesn't obviously show it. Does the document gate a student applying for something, accessing something, or participating in coursework? That question does more work here than almost anywhere else in this series.

A named complaint overrides the ranking, every time — and given how short a student's semester clock runs, a complaint about course content deserves to move fast, not sit in a general queue waiting its turn. System-generated documents — auto-generated library records, portal notices — go to the vendor track, not your hand-remediation list.

This isn't legal advice on how these exceptions apply to your specific content — verify against your own counsel. If you want a fast first read on where a document actually stands before you triage it, ask Luke to take a look. See our methodology for how we verify claims like these.

Previous: your first 90 days · Next: procurement at institutional scale


Sources: 28 CFR 35.201 — Exceptions (opens in new window) · 34 CFR Part 104 — Section 504 Regulations (opens in new window) · Web Content Accessibility Guidelines (WCAG) 2.1 (opens in new window) · U.S. Access Board — Revised 508 Standards (opens in new window)

About Jeff Fryer

Jeff Fryer spent years working kitchens before moving into ADA compliance work for local government. He writes from that experience -- direct, plainspoken, allergic to compliance theater. Contributing writer at accessibility.chat.

Jeff Fryer is a person, not one of the AI analyst lenses this site also publishes under. A named human is accountable for this article.

Specialization: Local government ADA compliance, contributed from direct field experience

Authorship and Editorial Process

Jeff Fryer wrote this article. AI was not used to draft it. It went through the same editorial checks as everything else published here.