ADA Title II
School District Website Accessibility Under ADA Title II
A district's website is part of how it delivers education: enrollment forms, lunch menus, bus routes, board agendas, the parent portal. The DOJ's web rule covers all of it, and public school districts are named explicitly among the state and local government entities it reaches.
Sources
Key takeaways
- Districts are covered: public K-12 schools, community colleges and public universities fall under ADA Title II.
- Your deadline follows population, not enrollment: it is the population of the jurisdiction the district serves.
- The portals are the hard part: enrollment, payment and gradebook systems are usually a vendor's software and usually the least accessible thing a district publishes.
- Staff-uploaded documents are the volume problem: every teacher who posts a scanned PDF adds to the pile.
Does school district website accessibility fall under the rule?
Yes. The DOJ's fact sheet on the web rule names public schools, community colleges and public universities among the entities covered by Title II. The regulation at 28 CFR § 35.200 sets WCAG 2.1 Level AA as the technical standard for the web content a public entity provides, directly or through a contract with somebody else.
In detail
The practical reading for a district is that "the website" is not one site. It is the district site, every school's site, the enrollment portal, the payment system, the transportation lookup, the board agenda archive and whatever the athletics department publishes. Each of those is web content the district makes available, so each is in scope.
Which compliance date applies to a district?
The rule splits public entities by the population they serve: April 26, 2027 for entities serving 50,000 or more people, and April 26, 2028 for smaller entities and special district governments. A school district is measured by the population of the jurisdiction it serves, not by how many students are enrolled, so a district in a large county can land on the earlier date even with modest enrollment. The deadlines guide walks through where the two dates come from.
Why are enrollment and gradebook portals the hardest part?
Because they are interactive and because a vendor built them. Multi-step enrollment forms, date pickers, file uploads for immunization records, payment flows for lunch accounts and gradebook dashboards are exactly the content a parent using a screen reader or keyboard alone cannot work around. They are also exactly the content a district does not control the source code for.
In detail
A vendor's claim that its platform is "fully accessible" is a thing to verify, not a thing to file. Ask for a current accessibility conformance report with a test date on it, put WCAG 2.1 Level AA in the renewal contract, and have the portal tested by somebody who does not work for the vendor. The vendor-run websites guide covers why the obligation stays with the district whoever operates the software.
What should a district do about its document library?
Triage it rather than try to fix all of it at once. The rule covers the documents people currently use to apply for, access or take part in your services: enrollment packets, handbooks, calendars, board agendas, permission forms. Conventional documents posted before your compliance date and no longer in use generally fall under the rule's preexisting-documents exception.
In detail
The structural fix is upstream. A district that keeps scanning paper and posting the image will regenerate the problem every semester, so the lasting answer is a template and an upload rule for staff: real text rather than a scan, headings in order, alternative text on anything that carries meaning, and a fillable form rather than a print-and-return PDF. Our accessible documents guide sets out what the rule covers and what an accessible PDF actually requires.