School District WordPress Accessibility
Most district sites are not maintained by a web team. They are maintained by two hundred people who each publish a few times a year, on a subsite per school, with a different person doing it every eighteen months. That is the actual accessibility problem, and it is not one a remediation pass alone can solve.
A district's date is not set by its enrolment
ADA Title II
April 26, 2027
Public entities with a population of 50,000 or more
About 8 months from today.
ADA Title II
April 26, 2028
Public entities with a population under 50,000, and special district governments
About 20 months from today.
Public school districts are public entities under ADA Title II, and the rule's two dates are keyed to population — the population of the area the district serves, not the number of students enrolled. Those are very different numbers. A district of 3,000 students can sit inside a service area well above 50,000 and land in the earlier group.
Confirm which figure applies to your district before you plan around it. Where the boundary is unusual — a district spanning several municipalities, a regional or intermediate unit, a district that shares services with neighbours — that is a question for your attorney, not for a vendor.
All four dates, in full
| Compliance date | Rule | Who it applies to |
|---|---|---|
| April 26, 2027 | ADA Title II | Public entities with a population of 50,000 or more |
| April 26, 2028 | ADA Title II | Public entities with a population under 50,000, and special district governments |
| May 11, 2027 | HHS Section 504 | Recipients of HHS federal financial assistance with 15 or more employees |
| May 10, 2028 | HHS Section 504 | Recipients of HHS federal financial assistance with fewer than 15 employees |
Where these dates come from. Verify current guidance before relying on any date for planning — both rules have already moved once.
- U.S. Department of Justice — ADA Title II web rule: ada.gov/resources/web-rule-first-steps
- U.S. Department of Health and Human Services — Section 504 deadline extension: hhs.gov press release
MakeWPCompliant provides technical accessibility services, not legal advice. How a rule applies to a specific organization is a question for current federal guidance and, where appropriate, qualified legal counsel.
Count your editors, not your pages
On a commercial site, remediation ends and the site stays fixed for a while. A district does not work like that. Between the day we finish and the compliance date, your staff will publish thousands of new items: newsletters, permission slips, event flyers, classroom pages, coaching updates, principal's messages.
If two hundred people can add content faster than anyone can correct it, page-by-page remediation is not a project. It is a subscription.
Which changes what the work should be. On a district engagement the majority of the value is in the layers that apply to everybody at once:
- Network theme Navigation, headers, focus behaviour, colour, the school switcher, the emergency banner. One fix, every school.
- Shared plugins Staff directories, calendars, news feeds, forms, document libraries — usually network-activated, so one correction covers all subsites.
- Templates and blocks The patterns editors reuse. Making the accessible version the default one is worth more than any amount of correction after the fact.
- Editor guardrails What the publishing screen permits, warns about, or quietly prevents — before anything reaches the public site.
- Existing content The genuinely per-page work, scoped to what is current and what people actually open.
Content still has to be corrected. But a district that leaves with only corrected content has bought the least durable half of the project.
The content types that are specific to schools
Generic accessibility advice does not mention any of these, and they are where district findings actually cluster.
- Board packets posted as one 400-page scanned PDF Separate document work from site work, and price it honestly
- Board meeting video published with automatic captions Treat automatic captions as a draft, not as captions
- Lunch menus embedded from a nutrition vendor Test the embed, then document it as a vendor dependency
- Athletics schedules pulled in by a third-party widget Establish where your site ends and the widget begins
- Teacher pages embedding Google Docs and Slides Fix the pattern staff were taught, not one teacher's page
- Staff directories with photos, no names in the markup One plugin template correction covers every school
- Event flyers uploaded as a JPEG of a poster A required text version in the template, not an editor's good day
- Twelve schools that each rebuilt the same quick-links grid One accessible block, made the default for new pages
Closures are the highest-stakes content you publish
A snow day, a lockdown, an early release. That announcement typically goes out through a mass-notification service, a social account and the website — and only the last of those is in scope for this work, which makes it easy to assume somebody else has it covered.
It is worth testing the closure banner in the state parents meet it, on a phone, before it is ever needed. It is a small component with an outsized consequence, and it is usually built by whichever vendor themed the site.
April 2027 is a deadline, not a starting date
If your public-sector WordPress site needs to meet the Title II technical requirements, start identifying the real remediation work now.