ADA Title II accessibility for school apps: what the 2027 deadline means

ADA Title II accessibility for school apps now runs on two deadlines. Public entities with a total population of 50,000 or more must meet WCAG 2.1 Level AA by April 26, 2027. Smaller entities and special district governments have until April 26, 2028. URBI builds parent facing surfaces that fall inside that scope.

Much of the content ranking for this question is out of date. It still names April 24, 2026, or rounds the two cohort dates into one. The Department of Justice moved both dates in an interim final rule effective April 20, 2026, and left the standard alone. Obligations vary by entity type and jurisdiction, so confirm your own position with counsel.

Which deadline applies to your district or campus?

Your deadline depends on how the rule calculates total population, not on how many students you enroll. The definition in 28 CFR 35.104 gives four methods, and the wrong one moves your date by a year.

Two traps sit inside that table. The first is calling a school district a special district because it is a single purpose body. The rule's definition expressly excludes independent school districts. The second is reading the poverty estimates as a student count. They estimate the district's population, adults included.

Both dates come from the Federal Register notice published in 2026. The standard did not move: ADA.gov states that WCAG Version 2.1, Level AA is the technical standard for state and local government web content and mobile apps.

What counts as web content and a mobile app in a school?

Far more than the district website. Section 35.200 reaches web content and mobile apps an entity provides or makes available "directly or through contractual, licensing, or other arrangements." That phrase pulls in your vendors.

• Parent and student portals. Registration, forms, grades, messaging, anything a family signs in to reach.
• Facility booking. Gym, auditorium, cafeteria, and field reservation flows, community rentals included.
• Payment flows. Tuition, activity fees, deposits, and ticketing checkouts.
• Mobile app content. Content inside an app the district provides, whether the district wrote it or licensed it.
• PDFs and office files. The rule defines conventional electronic documents as PDF, word processor, presentation, and spreadsheet formats. Handbooks, permission slips, board packets, and lunch menus land here.
• Third party content posted for you. A vendor posting under contract or license with the district is not outside the rule.

Standalone SMS and email alerts are a different analysis. This rule is written about web content and mobile apps, so review those channels with counsel under Title II's broader effective communication duty.

Which content is actually excepted?

Five exceptions exist, each narrower than districts expect. Section 35.201 lists them: archived web content, preexisting conventional electronic documents, content posted by a third party, individualized secured documents, and preexisting social media posts.

• Preexisting documents lose the exception when in use. The text carves out documents "currently used to apply for, gain access to, or participate in" the entity's programs. A 2023 field trip form families still fill out is in scope.
• Third party content is not excepted when you arranged it. The exception does not cover a party posting "due to contractual, licensing, or other arrangements with the public entity."
• The secured document exception covers documents, not portals. It applies to conventional electronic documents about a specific individual, their property, or their account that are password protected or otherwise secured. A login is not an exception to anything.
• Archived means archived. Kept only for reference, research, or recordkeeping, never updated, clearly marked as an archive.

Section 35.200 also allows relief where compliance would cause a fundamental alteration or undue financial and administrative burdens. That is a documented determination, not a scheduling preference.

Why did DOJ move the dates, and how should that change planning?

The extension was about capacity, not a softer standard. The 2026 notice says advanced technology, including "generative AI, does not yet reliably automate the remediation of inaccessible content at scale," and that staffing remains a significant challenge. Practitioners read it the same way. Jamie Axelrod, director of disability resources at Northern Arizona University and a past AHEAD president, told Inside Higher Ed in 2026: "Do not stop the efforts you've been engaged in to improve the accessibility" of course content and interfaces. Jarret Cummings, senior adviser at EDUCAUSE, told EdTech Magazine that "all relevant content, services and systems need to fully meet" the WCAG 2.1 AA standard.

DOJ's first steps guidance suggests sequencing by use: start with content people use to register for programs, submit forms and reservations, and pay bills. For a district that means enrollment, parent access, facility booking, payments, then safety notices.

What should districts ask a vendor, including URBI?

Ask every vendor for current accessibility documentation, then verify it yourself. Responsibility does not transfer with a contract, so a vendor's defect becomes the district's exposure.

Here is where URBI has to be straight with you. URBI runs much of the parent facing surface in a K-12 deployment: announcements with urgency levels and per parent read tracking, facility booking, visitor management with QR passes and a check in log, tuition and activity fee payments, an OTP gated public portal a grandparent or volunteer can use without downloading anything, and Arthur, the parent facing AI, answering by phone, text, email, and in app chat in ten languages. Arthur matters here in a way that is easy to miss. A call answered in a family's own language reaches households that will never open a web portal. That is not a substitute for a conforming interface, and we do not present it as one.

URBI has not published a WCAG 2.1 Level AA conformance report. We say so plainly rather than let a procurement checklist assume otherwise. Ask URBI for current accessibility documentation, and ask every other vendor in your stack the same question in writing before renewal. A vendor that answers vaguely is telling you something.

Questions worth putting in any bid: which product areas were tested, when, against which WCAG version, with which assistive technologies, by whom, what defects remain open, and on what timeline they close. Some buyers ask for more than the federal baseline. The University of North Carolina asks vendors to adhere to WCAG 2.2 Level AA and to supply updated documentation as products change.

What evidence of remediation should you keep?

Keep the record that shows the work happened, not just the final score. No federal retention schedule attaches to this rule, so treat the file as an internal control answering a complaint or a board question.

• A dated inventory of every site, app, portal, and document set, with owner and vendor named.
• Test reports from both automated and manual assessment. DOJ says "you won't be able to use automated testing tools alone," because scanners cannot test every aspect of accessibility.
• A defect log showing each issue, the fix applied, and a passing retest. Massachusetts guidance asks vendors for written validation naming the remediation technique and the testing method, and says an Accessibility Conformance Report alone is not sufficient.
• Vendor accessibility reports plus the test plan, results, and corrective actions.
• Contract language on accessibility, including obligations that survive product updates.
• Policies, named roles, and training records.
• Written reasoning for every exception claimed and every undue burden determination.

Deciding what to inventory first? The superintendent guide to school software and our overview of URBI for schools map the surfaces most districts run. The two nobody remembers to list are facility rental and visitor check in.

Frequently asked questions

Does the extension mean we can pause accessibility work until 2027?

No. The extension moved the WCAG 2.1 Level AA compliance dates. It did not create a period in which the ADA stops applying to district web content and mobile apps. Effective communication and nondiscrimination duties continue, and a family who cannot reach a form today can raise it today. DOJ's stated reason was capacity, not a change of position.

Our parent portal is behind a login. Does that exempt it?

No. The exception is written about conventional electronic documents that concern a specific individual, their property, or their account and are secured. It is not an exception for portals. The platform delivering those documents is web content or a mobile app, and the rule reaches it whether you built it or licensed it.

Does a vendor's accessibility report make our district compliant?

It is evidence, not a safe harbor. The public entity stays responsible for content and apps provided through contractual and licensing arrangements, and Massachusetts states outright that a conformance report alone is not sufficient. Check the date and version tested, test the workflows your families use, and put remediation obligations into the contract.

Do public university housing operations follow the campus or the town?

Usually neither. A public university that is an instrumentality of a state uses that state's combined decennial Census population under the rule's total population definition, which puts it in the 50,000 or more cohort. Housing follows the university's classification. Confirm your entity's legal status with counsel, since instrumentality turns on state law.

This is a procurement question as much as a web question. Every parent facing system you buy carries part of your obligation, and you cannot audit what you never asked about. To see how URBI handles parent communication, facility booking, visitor management, and payments in one place, or to request our accessibility documentation, write to hello@myurbi.co. Start with what URBI is, then URBI for student housing and multilingual resident communication.