ADA Title II K-12 Schools: Website Rules and Deadlines

ADA Title II K-12 requirements now come with firm web accessibility dates, and district leaders need to know which one applies to them. This guide explains what the Department of Justice (DOJ) rule requires, when your district must comply, and how to build a practical audit-and-fix plan. It is general information, not legal advice, so confirm decisions with your district’s counsel.

ADA Title II K-12: What the DOJ Web Rule Requires

Quick answer: The DOJ rule requires state and local governments, including public school districts, to make web content and mobile apps meet WCAG 2.1 Level AA. According to ADA.gov, districts must comply by April 26, 2027 if their governing population is 50,000 or more, and by April 26, 2028 if it is smaller.

Here is the who, what and when in brief:

• Who: State and local governments. The ADA.gov fact sheet lists public schools among its examples, and the duty extends to content that contractors post on a government’s behalf.
• What: Websites and mobile apps must meet WCAG 2.1 Level AA, the technical standard named in the rule.
• When: April 26, 2027 or April 26, 2028, depending on population.

The DOJ published the final rule in the Federal Register on April 24, 2024. An Interim Final Rule published on April 20, 2026 extended the compliance dates, as described in the DOJ fact sheet on the web rule.

Which Deadline Applies to Your District

A school district is not a special district government, so it follows the population-based dates below, per ADA.gov.

Which population counts depends on the district type. ADA.gov says a city school district uses the city’s population, a county school district uses the county’s, and an independent school district uses the most recent Small Area Income and Poverty Estimates. For a wider planning view, see our guide to Title II deadlines.

Example: a small rural district

Picture an illustrative rural county district with a few schools, one IT generalist and a website built on a common CMS. Its county population is under 50,000, so the 2028 date applies. The risk is not size but stretched staff: PDFs pile up, and the web page is updated by whoever has time. This district benefits from starting with the most-used pages and setting simple publishing habits now.

Example: a large urban district

Now picture an illustrative urban district in a city above 50,000 people, so the 2027 date applies. It has dozens of schools, a communications team, a student information system, a transportation app and many vendors. Its challenge is coordination: who owns each tool, which vendors can document accessibility, and how to test at scale.

The WCAG 2.1 AA Standard in Plain Language

According to the W3C, WCAG 2.1 is organized around four principles: perceivable, operable, understandable and robust. Each has testable success criteria at levels A, AA and AAA, and the DOJ rule points to Level AA.

In practice, that means things like text contrast of at least 4.5:1, text alternatives for images, captions for prerecorded video, full keyboard operation, labeled form fields and clear error messages. WCAG 2.1 also added AA criteria for reflow, non-text contrast, text spacing and status messages. You can read every criterion in the official WCAG 2.1 specification.

Newer versions exist, but the rule names 2.1. Teams that want to build ahead can review our overview of what changed in WCAG 2.2.

Will K-12 Get Its Own Rule?

The DOJ has signaled that separate rulemaking for K-12 may follow. The fact sheet we cite does not describe any such rule, so treat it as a possibility rather than a requirement. Whatever happens with separate ADA Title II K-12 rulemaking, the current rule and its dates are the planning baseline.

Track updates on the DOJ’s ADA web guidance page and ask counsel how any change would affect your timeline.

Content Most Districts Overlook

Homepages get attention. The trouble usually sits elsewhere. The points below draw on the exceptions and examples in the ADA.gov fact sheet.

PDFs and documents

Word, PDF, presentation and spreadsheet files posted before your compliance date can be excepted. That exception does not cover documents currently used to apply for, access or participate in district services, and it ends if the file is later updated. Enrollment packets, lunch applications and current handbooks deserve a fix.

Parent and student portals

Individualized PDFs about one person in a password-protected account may be excepted, but the portal itself is not. HTML views, such as a grade page, generally need to meet WCAG 2.1 AA.

Forms

Registration, permission slips and transportation requests are where barriers cost people the most time. The fact sheet’s own example of a violation is an online form that takes far more effort for a person with a disability to complete.

Videos

WCAG 2.1 requires captions for prerecorded and live audio in synchronized media, plus audio description for prerecorded video at Level AA. Board meeting recordings and school announcements are common gaps.

Third-party tools

Calendars, scheduling tools, maps and payment systems added by a government are not excepted, according to ADA.gov. Content posted by a vendor you hire is not excepted either. Only posts by outside members of the public, such as comments on a message board, are likely excepted.

A Simple Audit-and-Fix Plan

1. Confirm your date. Work out which population applies and record it.
2. Inventory. List every website, portal, app, video library and document source, with an owner for each.
3. Prioritize by use. Start with enrollment, calendars, forms, payments and emergency notices.
4. Test twice. Run an automated scan, then add manual checks with a keyboard and a screen reader. Automated tools cannot catch every barrier.
5. Fix and ask vendors. Repair what you control, and request accessibility documentation and fixes from vendors.
6. Set habits. Train staff who upload content and re-test on a schedule.

An AI-powered widget like Accessify can handle many common issues automatically on platforms such as WordPress, and it installs in about 2 minutes. Complex pages, forms and PDFs still need manual testing and fixes in code or at the source. More habits are covered in our web accessibility best practices.

Do not plan around the minor-noncompliance idea. ADA.gov says it is narrow, the government must prove the gap would not change access, and it cannot be used to avoid trying to meet WCAG 2.1 AA. Even where an exception applies, districts must still provide effective communication, so keep an accessible alternative ready on request.

How Accessify, UserWay, accessiBe and AudioEye Compare

The reference sources for this article do not cover vendor features, so this table limits itself to what Accessify states publicly and to what you should verify yourself. UserWay, accessiBe and AudioEye are all well-known providers with public product pages, which makes side-by-side evaluation straightforward.

Accessify suits smaller districts with a standard site that want fast automated fixes. A large urban district with student portals and many vendors may be better served by a manual audit, a managed service or an enterprise platform. Because Accessify publishes the table’s pricing, check the vendor’s site for current pricing before deciding.

ADA Title II K-12 Action Checklist

Use this list as a starting point for your ADA Title II K-12 readiness plan:

• Confirm whether 2027 or 2028 applies to your district.
• Name an accessibility owner and list every site, app and portal.
• Fix current enrollment, application and registration documents first.
• Caption videos and add audio description where needed.
• Request accessibility documentation from every third-party vendor.
• Combine automated scans with manual keyboard and screen reader tests.
• Keep an accessible alternative ready for any content you cannot yet fix.
• Ask counsel about any K-12 rulemaking news.

Frequently Asked Questions

What is the Title II web accessibility rule?

It is a Department of Justice regulation that sets WCAG 2.1 Level AA as the technical standard for web content and mobile apps of state and local governments, including public schools. According to ADA.gov, it covers services offered online, including content provided through contractors.

How much does it cost to make a district website accessible?

The sources used here give no cost figure, and costs vary with site size, document volume and vendor systems. Accessify plans start from $19/month for the widget, but check the vendor’s site for current pricing. Budget separately for manual testing, PDF repair and vendor fixes.

What should a district do first?

Confirm your compliance date, then inventory every site, portal, app and document source. A written inventory shows where the most-used content lives and which vendors are involved, so you can fix enrollment forms, calendars and emergency notices before lower-traffic pages.

Can an accessibility widget make our site compliant on its own?

No. A widget can fix many common issues automatically, but it cannot guarantee legal compliance. PDFs, third-party portals and complex forms usually need manual testing and fixes at the source or by the vendor. Treat a widget as one layer in a wider plan.

Do old PDFs on our website need to be fixed?

Not always. According to ADA.gov, files posted before your compliance date can be excepted, but not if people currently use them to apply for or access services, or if you edit them later. Enrollment forms still in use should be remediated.

What mistake should districts avoid?

Assuming the vendor has it covered. ADA.gov says content a contractor posts for you, and tools such as calendars or payment systems you add, are generally not excepted. Ask for accessibility documentation and write accessibility requirements into contracts.

Want a faster start on the fixable issues? Explore Accessify at accessify.app and pair it with manual testing.