You're the 504 Coordinator: The Law Behind the Job
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.
Three federal laws touch your digital content, and they fail differently. Confusing them is how things fall between the cracks.
Unlike most sectors in this series, your role isn't optional. Districts receiving federal funds with fifteen or more employees must designate a 504 coordinator and adopt a grievance procedure — which in practice means essentially every district in the country. So you exist, by law. What you probably don't have is digital training, a technology budget, or anyone who's explained how the three federal regimes touching your content actually relate to each other.
Let me do that now.
Three laws, three different jobs
Title II of the ADA and Section 504 of the Rehabilitation Act (opens in new window) impose a general nondiscrimination duty on everything you offer digitally — to students, to parents, and to the public. That duty is owed to everyone, not only to students with IEPs and 504 plans, and it's enforced through effective communication and, now, the web rule's WCAG standard (opens in new window).
FAPE — a free appropriate public education — is a separate, individualized obligation. Accessible technology serves that right but doesn't satisfy it by itself.
And IDEA's accessible-instructional-materials machinery, built around the National Instructional Materials Accessibility Standard (opens in new window), requires that students who need specialized formats get them in a timely manner — "at the same time as other children receive instructional materials" — and requires specific contract language when you purchase instructional materials. Since federal guidance clarified that "print instructional materials" includes digital instructional materials, that NIMAS contract language belongs in your digital curriculum purchases, not just textbook adoptions.
The practical translation: web-rule work protects the district as a whole. NIMAS clauses and timely-manner delivery protect individual students. A coordinator running both tracks under one inventory is the only way they don't fall between the cracks of each other.
Which deadline is yours
School districts are not "special district governments" under the ADA's web rule — the rule's definition specifically excludes independent school districts from that category — so your compliance tier is set by ordinary population rules. The mechanism depends on what kind of district you are: a city school district uses the city's population, a county district uses the county's, and an independent school district uses the federal small-area population estimate published for the district itself. That last one catches people off guard — an independent district serving part of a large metro can still land in the later compliance tier on its own separate estimate. Look yours up specifically rather than assuming.
I'm not printing dates here. They've moved once by federal rulemaking already and the extension is being litigated.
The password-protected trap
The web rule's exception for individualized password-protected documents covers content about one specific student or account — a report card, an individual invoice. It does not except your learning management system, your curriculum platforms, or anything students and parents log into to actually participate in school. Content used to apply for, access, or participate in your programs is covered even behind a login. Assume your LMS and everything inside your single-sign-on portal is fully in scope, because it is — this is the single most common mistake I see new coordinators make.
What OCR enforcement actually looks like
The Office for Civil Rights (opens in new window) has run web-accessibility enforcement in K-12 for a decade, and resolution agreements as recent as this year have required districts to audit and correct barriers across their websites, PDFs, videos, social media, third-party platforms, and mass notification systems, all at once. The pattern is stable: audit against WCAG-aligned criteria, a corrective action plan with real deadlines, written policy, designated personnel, training, and a public barrier-reporting channel. That's not a coincidence — it's the table of contents of this whole series.
OCR's complaint process is free and parents know it well. Your intake log and response times matter more in this sector than almost anywhere else in this series, precisely because the complaint route is so accessible to the people filing them.
None of this is legal advice, and it doesn't substitute for your own counsel confirming which regimes reach your specific district. If you want a fast first read on how a specific page or PDF actually measures up against WCAG 2.1 AA (opens in new window), ask Luke to check it. Our WCAG reference and methodology cover how we verify claims like these.
Next: your first ninety days — what to actually do with all of this, starting Monday.
Sources: 34 CFR Part 104 — Section 504 Regulations (opens in new window) · 28 CFR Part 35, Subpart H — Web and Mobile Accessibility (opens in new window) · NIMAS Regulation — 34 CFR 300.172 (opens in new window) · OCR Resolution Agreement Example — Olentangy Local School District (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.