A Large K-12 School District: Managing 47 School Websites From One Accessible Platform
One OCR complaint at a large K-12 school district. 47 school sites scattered across Wix, WordPress, Squarespace, and abandoned vendor platforms. Three weeks later, the district ran on one platform with a single dashboard showing PDF risk across every school.
47
School sites migrated
3 wks
District-wide migration timeline
8,400+
PDFs scanned across all sites
1
Compliance dashboard for all 47 schools
The OCR Investigation Context
Fall 2025. The Department of Education's Office for Civil Rights opened a compliance review of a large K-12 school district in the SLED sectorafter a parent filed a complaint on behalf of a student with a visual impairment. The parent said screen reader software couldn't read the student handbook, the district's special education procedural safeguards document, or several school event calendars. That's the kind of complaint that moves fast.
OCR's first data request asked the district for four things:
- A complete inventory of all district-managed and school-managed websites and web applications
- Documentation of any accessibility policies or standards currently in effect
- A list of all digital documents published in the past 24 months that relate to programs or services available to students or families with disabilities
- Records of any accessibility complaints received in the prior 3 years and how they were resolved
Question one broke the whole thing open. The district ran a primary site at the district level, plus 47 individual school sites, but those 47 sites weren't on a common platform. They were spread across at least 6 different hosting arrangements: Wix (12 sites), an abandoned WordPress multisite install (8 sites), Squarespace (6 sites), and a grab bag of legacy vendor platforms (21 sites across three different vendors). No central accessibility oversight. No shared template. No way for the district to verify anything about its own web properties.
The Web Fragmentation Problem
The district's technology director called it “web sprawl.” And it's the kind of sprawl every K-12 district recognizes. A principal wanted a site that looked different from the last one. A parent group offered to “help” by spinning up a Wix page. Each time the answer was yes, the district's web footprint got a little more fractured. Accessibility paid the price:
Wix (12 sites)
Wix accessibility has gotten better, but it's uneven. Heading hierarchy wasn't enforced. PDF uploads got zero accessibility scanning. Navigation looked different on every site.
Abandoned WordPress multisite (8 sites)
The install hadn't been touched since 2021. Themes were outdated. Plugins were unpatched. Content had been added for years without a single accessibility review. One site hadn't been updated at all since 2022.
Squarespace (6 sites)
Squarespace WCAG behavior depends on the theme, which means it's inconsistent. Color contrast failed on 4 of 6 sites. No PDF scanning on any of them.
Legacy vendor platforms (21 sites)
Three different vendors. Three different sets of accessibility capabilities. One vendor had killed support entirely, which meant two schools were running on software nobody supported anymore.
Pre-migration platform breakdown
47 sites
School sites split across at least 6 hosting arrangements, none of them talking to each other.
The 3-Week Migration
The technology team picked WPPersona for three reasons. One: multi-site architecture that keeps central governance without stripping per-school content autonomy. Two: PDF scanning that can be enforced across every school from one control panel. Three: migration support that didn't hand each school secretary a second job.
The district's primary site went first. That build set the shared template, navigation, color palette, and brand standards every school site would inherit. The technology director and the assistant superintendent of communications signed off on the template before any school site moved. Three template variations followed (Elementary, Middle, High) with age-appropriate accents. Accessibility standards stayed identical across all three.
24 school sites moved in parallel using WPPersona's batch migration tooling. For each school, the primary content came across first: staff directory, calendar, handbook, key program pages. Principals and office managers reviewed their sites in staging and approved them. Anything that couldn't be migrated cleanly (inaccessible PDFs, Flash-dependent media, dead links) got flagged for replacement instead of dragged into the new environment.
The remaining 23 school sites moved. At the same time, the bulk PDF audit tool scanned every document across every site. 8,423 PDFs in total. The output was a district-wide risk report. The technology director opened the compliance dashboard and saw the shape of the problem by school: 3 schools had zero Critical documents, 11 schools had more than 50 Critical documents each. Remediation staff were allocated by school risk level. All 47 sites cut over on the last day of Week 3.
Cumulative sites migrated (3-week rollout)
47 of 47 live
1
District site + template foundation
24
School sites batch-migrated in Week 2
23
Remaining sites plus 8,423 PDFs scanned
The Central Compliance Dashboard
For the technology director, the compliance dashboard changed the job. Before migration, there was no way to know the district's aggregate accessibility risk across 47 school sites. None. After migration, one screen answered it:
District-wide PDF risk score
An aggregate score across all 47 sites, updated in real time as new documents get uploaded and scanned.
Per-school risk ranking
Schools ranked by PDF risk level. High-risk schools flag automatically for the technology team.
Document type breakdown
Risk broken down by category: handbooks, agendas, curriculum guides, financial reports.
Upload activity log
Every PDF uploaded across every school, with scan result and the account that uploaded it.
Remediation progress tracking
As Critical and High-risk documents get fixed, progress bars move in real time.
OCR evidence export
One-click export of a compliance evidence package formatted for OCR submission.
OCR Agreement Resolution
The district shipped its OCR response package within 90 days of the initial data request. It included the platform migration documentation, the district-wide PDF risk report, remediation progress tracking, and a forward-looking compliance maintenance plan. OCR accepted it. The district and OCR signed a voluntary resolution agreement that named WPPersona's ongoing PDF scanning as the mechanism for demonstrating continued compliance.
“OCR asked us how we planned to maintain compliance going forward, not just fix the current problems. Being able to point to a platform that enforces accessibility at every upload, across all 47 sites at once, was the answer they were looking for. That was the credibility the voluntary resolution needed.”
Director of Technology, K-12 School District
Managing Multiple School Websites?
If your district runs dozens of school sites, WPPersona's multi-site architecture and central compliance dashboard were built for exactly that.
Schedule a Free Demo