Altwise

ADA Title II web rule for public school districts and charter schools: dates, what's covered and practical fixes

Plain-English guide to the DOJ ADA Title II web accessibility rule for US public K-12 school districts and charter schools: how a district's 2027 or 2028 date is worked out, WCAG 2.1 AA, vendor portals, board agendas, meeting captions, calendars, parent portals, forms and a calm first-steps plan.

A public school district's website carries a lot: enrollment and registration, lunch-account top-ups and fee payments, board agendas and minutes, meeting video, calendars and closure alerts, staff directories, athletics schedules and the parent portal. Parents, guardians, students, staff and community members with disabilities use all of it, often on a phone, with a screen reader, magnification or voice control. The U.S. Department of Justice's ADA Title II rule sets a technical standard and dates for state and local government web content, and DOJ's fact sheet lists "public schools" among its examples of state and local governments. This guide summarises what DOJ has published and then covers the fixes that matter most on school sites. Always check the official pages linked here; this guide is not legal advice.

The dates (extended in April 2026)

DOJ published the rule on April 24, 2024. On April 20, 2026, an interim final rule in the Federal Register pushed the compliance dates back one year. The current dates, from 28 CFR 35.200 and the ADA.gov fact sheet:

Title II web rule compliance dates (sources: 28 CFR 35.200 and the ADA.gov fact sheet)
Public entityCompliance date
Total population of 50,000 or more (other than a special district government)April 26, 2027
Total population under 50,000April 26, 2028
Any special district governmentApril 26, 2028

How a school district's date is worked out

This is the part people most often get wrong, so here is what the sources say, word for word where it matters.

Charter schools: neither the fact sheet nor the rule text we checked mentions charter schools by name. How a charter school is set up varies by state (for example, whether it is its own entity or part of a district or other public body), and that can affect which population figure applies. Read the "total population" definition in 28 CFR 35.104, check with your authorizer, and ask your attorney rather than guessing. The same goes for any district whose type isn't obvious.

Other laws still apply. In the 2024 final rule, DOJ notes that the Department of Education's regulations implementing IDEA and Section 504 of the Rehabilitation Act have longstanding obligations for covered schools, and says the web rule "builds on, and does not supplant, those preexisting requirements". This guide covers the website side only.

The standard and what's covered

Under 28 CFR 35.200, web content and mobile apps a public entity provides "directly or through contractual, licensing, or other arrangements" must meet WCAG 2.1 Level A and AA. For a district that usually includes vendor tools families reach from your site: enrollment and registration systems, lunch-account and fee-payment portals, the student information system's parent portal, the board-meeting platform, the athletics schedule service and the district app. The rule has limited defences for fundamental alteration or undue financial and administrative burdens, which an attorney should advise on.

The exceptions, briefly. 28 CFR 35.201 lists exceptions, each with conditions: archived web content; conventional electronic documents posted before your compliance date, unless they're still used to apply for, access or take part in a service; content posted by third parties not posting for you; individualized, password-protected documents about a specific person, property or account; and social media posts made before your compliance date. The fact sheet gives a school example: an old sample ballot for a school board election posted in 2014 would probably fall under the preexisting-document exception. A current enrollment packet or this year's supply list probably wouldn't. Read the exact text before relying on any exception.

The links to WCAG criteria below go to the W3C's WCAG 2.2 "Understanding" pages, which also explain the 2.1 criteria the rule uses. Where a tip goes beyond WCAG 2.1, we say so.

Where school websites usually struggle

1. Enrollment, registration, lunch-account and payment portals

These are usually vendor products. Ask each vendor for an accessibility conformance report (a VPAT) for the version you use and their WCAG 2.1 AA plan, and test the main tasks yourself: register a new student, add money to a lunch account, pay a fee. See our VPAT guide. On your own pages, the link to each portal should say what it is in text, not just show a vendor logo. (WCAG 2.4.4, WCAG 1.1.1)

<a href="https://pay.example.com/district">Add money to a school lunch account</a>
<a href="https://enroll.example.com/district">Register a new student for 2027-28</a>
<!-- example URLs and wording -->

2. Board agendas, minutes, policies and scanned PDFs

A scanned PDF is a picture to a screen reader. Publish agendas, minutes and policies as web pages or tagged, text-based PDFs, and give each link a clear name with the date. (WCAG 1.1.1, WCAG 1.3.1, WCAG 1.4.5) See accessible PDFs.

<a href="/board/2027-03-09-agenda.pdf">Board meeting agenda, March 9, 2027 (PDF, 180 KB)</a>
<!-- example values -->

3. Board meeting video and livestreams

Recorded board meetings need accurate captions; raw auto-captions often get names and motions wrong. Under WCAG 2.1 AA, live streams with audio also need live captions. Graduation and event videos you post need captions too. (WCAG 1.2.2, WCAG 1.2.4) See video captions.

4. Calendars and closure alerts

District calendars must work with a keyboard and list events as text, not only as coloured squares. Snow-day, weather and emergency closure banners should be real text near the top of the page, not an image or a graphic posted to social media only. A banner that appears after the page loads should be announced. (WCAG 2.1.1, WCAG 1.4.1, WCAG 4.1.3)

<div class="alert" role="status">
  <h2>All schools closed Tuesday, January 12</h2>
  <p>Due to ice, all district schools and offices are closed. Meals for students: see the <a href="/closures">closure page</a>.</p>
</div>
<!-- example values -->

5. Staff directories

Directories are often a grid of photos with names baked into the image or only in a pop-up. Use real text for each person's name, role, school and email, a search field with a visible label, and a result count that is announced. (WCAG 3.3.2, WCAG 4.1.3)

<label for="staff-q">Search staff by name, school or role</label>
<input id="staff-q" type="search">
<p role="status">12 staff members found.</p>
<!-- example values -->

6. Athletics and activities schedules

Schedules posted as a screenshot or a photo of a printed sheet can't be read by a screen reader or resized. Use a real table with header cells, or the schedule service's text view, and say "home" or "away" in words, not only by colour. (WCAG 1.3.1, WCAG 1.4.1) See accessible tables.

<table>
  <caption>Varsity volleyball, fall 2027 (example values)</caption>
  <tr><th scope="col">Date</th><th scope="col">Opponent</th><th scope="col">Home or away</th><th scope="col">Time</th></tr>
  <tr><td>Sep 7</td><td>Example High</td><td>Home</td><td>6:00 PM</td></tr>
</table>

7. Parent portal logins

Let password managers fill the username and password (don't block paste), and give any session timeout a warning and a way to extend, because filling in a long form with assistive technology takes time. (WCAG 1.3.5, WCAG 2.2.1) WCAG 2.2 goes further than the rule's WCAG 2.1 standard with 3.3.8 Accessible Authentication: no puzzle CAPTCHA or memory test as the only way in. Offering an alternative, such as an emailed sign-in link, helps every parent. See login and CAPTCHA fixes.

<label for="user">Email or username</label>
<input id="user" name="username" autocomplete="username">
<label for="pw">Password</label>
<input id="pw" name="password" type="password" autocomplete="current-password">
<div role="alert" hidden id="timeout-warn">You'll be signed out in 2 minutes. <button type="button">Stay signed in</button></div>

8. Forms: enrollment, transportation, volunteer and records requests

Every field needs a visible label (not just placeholder text), required fields marked in words, errors that say what to fix in text, and autocomplete on name, address and contact fields so parents don't retype them. (WCAG 3.3.2, WCAG 3.3.1, WCAG 1.3.5) See form error messages.

<label for="g-name">Parent or guardian full name (required)</label>
<input id="g-name" name="guardian_name" autocomplete="name" required>
<label for="g-email">Email (required)</label>
<input id="g-email" name="guardian_email" type="email" autocomplete="email" required aria-describedby="g-email-err">
<p id="g-email-err" class="error">Enter an email like [email protected].</p>
<label for="dob">Student date of birth</label>
<p id="dob-hint">For example, 09/14/2019</p>
<input id="dob" name="student_dob" inputmode="numeric" aria-describedby="dob-hint">
<!-- example values -->

9. Contrast, zoom and reflow

School colours on white or white text over campus photos often fail. Check text contrast of at least 4.5:1, that text can be enlarged to 200%, and that pages work at 400% zoom without sideways scrolling. Give each page a unique title and a page language. (WCAG 1.4.3, WCAG 1.4.4, WCAG 1.4.10, WCAG 2.4.2, WCAG 3.1.1) Try our contrast checker.

A calm first-steps plan

  1. Work out your date with the steps above and write down the figure and source you used.
  2. Inventory what you provide online: district and school sites, current PDFs and forms, vendor portals, meeting video, apps and social accounts.
  3. Ask each vendor for a VPAT and their WCAG 2.1 AA plan, and add accessibility terms to renewals.
  4. Fix the most-used paths first: home page, closures, enrollment, lunch payments, calendar, board agendas, contact.
  5. Convert current documents that families still use to web pages or tagged PDFs.
  6. Caption new meeting video and plan for live captions.
  7. Publish an accessibility statement with a way to report problems; adapt our template. Train the people who post content at each school, and keep checking with a maintenance plan.

Common mistakes

A 15-minute check you can do today

  1. Using only Tab, Shift+Tab, Enter and Space, get from the home page to the latest board agenda and open it. Can you select the text?
  2. Find the "add lunch money" link. Does it say what it does in words?
  3. Submit an enrollment or contact form empty. Do the errors say what to fix?
  4. Play the last board meeting video. Are there captions, and are names spelled right?
  5. Find this week's athletics schedule. Is it text or a picture?
  6. Zoom to 400% on the home page. Can you still reach the menu and the closure banner?
  7. Run the free homepage scan for code-level problems.

What an automated scan can and can't do

An automated scan, including ours, quickly finds a useful share of WCAG issues on the pages it visits, such as missing alt text, unlabelled fields and buttons, low contrast and missing page language. It can't confirm full WCAG 2.1 AA conformance, sign in to a parent portal or payment system, judge caption accuracy or read scanned PDFs, so manual checks and vendor reports are still needed. Our Fix-Pack scans up to 10 pages and gives copy-paste fixes; your web team or vendor applies them. We don't certify compliance or offer legal advice.

Related: ADA Title II rule for small towns, libraries and special districts, private and independent school websites, childcare and preschool websites, WCAG 2.2 explained.

This is general information, not legal advice, and it doesn't certify compliance with the ADA or any law. Dates and rules can change; check ADA.gov for the latest, and ask your attorney about your district's situation.

Want the fixes written for you?

Start with a free homepage snapshot. The $149 Fix-Pack scans up to 10 pages and gives copy-paste fixes for your platform within 48 hours, with a 14-day refund promise. See a sample report first.

This is general technical guidance, not legal advice, and it does not certify compliance with the ADA or any law.

Related guides

All guides

This guide is general technical information, not legal advice. Following it does not certify ADA or any legal compliance. Automated checks find only part of accessibility barriers.

Check your own site

Run a free homepage snapshot to see your top 3 issues in about a minute, or order the $149 Fix-Pack for up to 10 pages with copy-paste fixes for your platform.

Get my free snapshot