Skip to content
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
A black and white icon of a government building with columns, enclosed in a document-like outline with two circular fasteners at the top corners. A blue checkmark symbol is placed inside a small circle at the top of the building. Below the icon, bold black text reads

Title II Forum

E

emilie.brown

@emilie.brown
About
Posts
1
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • How Are Organizations Making Thousands of PDFs Accessible Without It Taking Years?
    E emilie.brown

    This question comes up constantly once organizations complete an accessibility audit. Someone runs a scan, finds out they have 30,000+ PDFs sitting in a document library or LMS, does the math on manual remediation, and realizes that finishing everything one document at a time could take years.

    So how are organizations actually getting through this without a multi-year backlog? A few patterns show up consistently in the ones that pull it off.

    1. They stop treating every PDF the same

    Not all 30,000 documents are equal. The teams that move fast triage first:

    • High traffic, high complexity (course materials, public forms, financial reports) → gets full attention, often human-reviewed
    • High traffic, low complexity (simple flyers, single-column text docs) → near-fully automatable
    • Low traffic, low complexity → automate and batch, don't overthink it
    • Low traffic, rarely accessed archival content → may legitimately qualify for an archive exception depending on the applicable regulation, instead of full remediation

    Doing this sorting up front is what turns "30,000 documents" into "actually, 22,000 of these are simple and can go through automation almost untouched."

    2. AI handles the mechanical 80%, humans handle the judgment 20%

    This is the actual unlock. Today’s modern document remediation platforms use AI to automate:

    • Structural tagging (headings, lists, tables of contents, reading order)
    • Alt text generation for images at scale, including specialized content like STEM diagrams, charts, and math notation
    • Table structure detection and tagging
    • Form field tagging

    Some platforms report automating roughly 90% of the tagging work this way. That's the difference between "a person opens each file and manually tags every element" and "a person reviews and approves what the system already did." One is measured in minutes per document; the other in hours.

    Humans still matter, reviewing AI-generated alt text for accuracy, handling genuinely irregular layouts, and doing final QA before anything ships. But they're reviewing, not building from scratch.

    3. They stop outsourcing 1:1 and start batching

    Sending every file to a vendor for individual manual remediation doesn't scale any better than doing it in-house manually, you're still paying for human hours per document, just someone else's. Orgs that get through large backlogs faster typically use a hybrid model: self-service automated remediation for the easy majority, with outsourced expert remediation reserved for the genuinely complex minority (scanned documents, dense multilingual content, heavily irregular tables).

    4. They build it into the pipeline instead of doing a one-time sprint

    The backlog only gets bigger if new inaccessible documents keep getting added while you're working through the old ones. Orgs that actually close the gap add automated remediation/tagging at publish time going forward, so the "thousands of PDFs" problem doesn't regenerate itself every semester or fiscal year.

    What this looks like at scale, in practice

    Publishers dealing with legacy content libraries in the millions of documents have reported turnaround times cut significantly and throughput increased by an order of magnitude when shifting from manual, post-production fixes to AI-driven workflows integrated earlier in the content pipeline, this is showing up right now with publishers racing to get ahead of the ADA Title II vendor requirements. Similarly, government and municipal document libraries, think meeting minutes, budget reports, public forms, are increasingly being processed this way rather than farmed out page-by-page.

    We've seen more organizations moving toward AI-assisted remediation because manual workflows simply aren't keeping up with document volume. Is that what you're seeing too?

  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Recent
  • Tags
  • Popular
  • Users
  • Groups