All resources
Case StudyBy Logan Nathan · Jul 2026 · 9 min read

A Large K-12 School District: Remediating 3,400 PDFs Before the DOJ Deadline

47 schools. 3,400 PDFs stacked up over 15 years. The district cleared 90% of the high-risk pile in 90 days, and they did it without adding a single seat to the web team.

3,400

Total PDFs in district archive

2,100

High-risk PDFs identified

90%

High-risk PDFs cleared in 90 days

47

Schools covered by the platform

15 Years of PDFs, One Deadline

The district serves 34,000 students across 47 schools, part urban, part rural. Like most K-12 districts in the SLED sector, staff had been posting documents to the site for 15 years, long before accessibility was a legal requirement for local government. When the technology director sat down in early 2026 to size the problem, the best guess was somewhere between 2,000 and 4,000 PDFs across the main district site and 47 school pages. The real number, after a full crawl, was 3,412.

Here's how the archive broke down by document type:

Board meeting agendas and minutes

847 filesMixed. Older scanned minutes fell into Critical.

Student and family handbooks

423 filesHigh. Multi-year versions, many image-only.

Course catalogs and program guides

389 filesHigh. Dense tables, charts, no alt text.

Athletics schedules and directories

612 filesMedium. Mostly text, some missing document titles.

Budget documents and financial reports

298 filesHigh. Spreadsheet exports with untagged tables.

Curriculum maps and pacing guides

843 filesCritical. Staff-created scans, no text layer.

The old CMS had zero document scanning. Staff at all 47 schools uploaded whatever they wanted, whenever they wanted, with no central review. The district's two-person web team had no line of sight into what was going out at the school level. During the initial crawl they found 14 schools had posted scanned handbooks that never got run through OCR. Fifteen years of pretty-looking, screen-reader-hostile documents.

PDF archive by document type

3,412 files

Six document categories collected across the district site and 47 school pages.

Board meeting agendas and minutes
847
Curriculum maps and pacing guides
843
Athletics schedules and directories
612
Student and family handbooks
423
Course catalogs and program guides
389
Budget documents and financial reports
298
Board minutes plus curriculum maps1,690 of 3,412
Board minutes and curriculum maps carried nearly half the archive between them, and both categories skewed toward image-only scans.

Why a Memo Wasn't Going to Work

The technology director's first instinct was the one most districts try first. Draft a new policy. Send a memo. Ask school webmasters to review their own documents. They piloted it with three schools for six weeks. Response rates hit 20%, and the documents that did come back were still failing. School staff aren't accessibility specialists. Handing them a PDF/UA checklist and expecting compliance is like handing a math teacher a legal brief and expecting an appeal.

So the district switched strategy. Point one tool at the whole domain and let it do the counting. WPPersona's bulk PDF audit scanned all 3,412 documents in under four hours. Every document got scored on five criteria: presence of /MarkInfo in the PDF dictionary, logical reading order, text layer completeness (OCR absence flags image-only files), document title metadata, and heading structure integrity. The output wasn't a dashboard. It was a spreadsheet a compliance officer could actually work from.

Risk Classification Results

Critical (image-only, no text layer)734 documentsOCR plus full remediation required
High (tagged but failing 3+ criteria)1,366 documentsStructured remediation workflow
Medium (1 to 2 minor failures)891 documentsStaff-led quick fixes
Low (passing all major criteria)421 documentsNo action required

PDF archive by risk tier (baseline scan)

3,412 total

Full crawl of the district site plus 47 school pages, scored on five PDF/UA criteria.

Critical
734
High
1,366
Medium
891
Low
421
Critical plus High (the DOJ-first pile)2,100 of 3,412
Critical and High together made 2,100 documents, the pile a DOJ investigator would open first.

The 90-Day Remediation Workflow

Month 1: Critical Documents

Start where the lawsuits come from. The 734 Critical documents were image-only scans, which means a screen reader hitting them returned either silence or a garbage string of characters. That's the exact scenario DOJ investigators ask about first. The district contracted an outside remediation vendor on a per-document rate. WPPersona's export function generated a work order list in one click, sorted by school so multiple vendors could work in parallel without stepping on each other. By Day 30, 680 of 734 Critical documents had been fixed, re-uploaded through WPPersona's upload scanner, and verified.

Month 2: High-Risk Documents and Staff Training

The 1,366 High-risk documents got spread across district staff. WPPersona's upload interface shows the person doing the uploading exactly what failed and how to fix it, with step-by-step instructions for Microsoft Word exports and Adobe Acrobat tagging. Instead of a memo, staff got feedback the moment they tried to publish. The technology team ran four 90-minute training sessions, one per school cluster. After training, first-attempt fix rates hit 85%. The other 15% got kicked back to the vendor. No arguments about who owns what.

Month 3: Verification and Forward Prevention

By Day 85, 89.7% of High-risk documents were cleared. The technology director ran a district-wide re-scan to confirm. The bigger win was the gate. WPPersona's upload scanner now blocks any PDF that fails the Critical or High-risk threshold, forcing the staff member to either fix the document or post an accessible HTML alternative. It turned on across all 47 school sites at once. No per-site config, no admin work at the building level.

Remediation progress across 90 days

90% cleared

0%25%50%75%100%Day 30Day 85680 of 73489.7% of 1,366Day 0306090Days since kickoff
Critical (734)High-risk (1,366)
Month 1 knocked out the Critical pile. Month 2 and 3 chased the 1,366 High-risk documents through the staff workflow.

Staff Workflow Changes

The historical cleanup mattered. The change in daily habit mattered more. Before, a school secretary could push any file, in any format, to the live site with one click. Now every PDF hits an automated accessibility check before it ever reaches the public URL.

Staff pushback came fast. Some called the gate an extra hoop. But within two months something shifted. The technology team noticed staff were building better Word documents on the front end because they'd figured out that a properly structured Word export passes the gate first try. The training paid itself back. Fewer rejections, fewer remediation cycles, and school offices weren't re-fixing the same handbook every August.

“Before, we had no idea what was being posted to school sites. A secretary would put up a scanned handbook, and it would sit there for three years with no one knowing it was completely unreadable to a screen reader. Now that gate catches everything before it goes live. It's changed how people think about documents.”

Director of IT, K-12 School District

Sitting on a PDF Archive You Can't Count?

WPPersona's bulk PDF audit scans your whole document archive in hours and hands back a prioritized remediation plan. See it run on your own domain.

Schedule a Free Demo