# When is your school district’s ADA Title II web deadline?

Canonical page: https://districtproof.io/resources/ada-title-ii-deadline-school-districts

The DOJ’s current guidance sets April 26, 2027 for public entities with 50,000 or more residents and April 26, 2028 for smaller entities. School districts use the applicable resident population—not student enrollment. Confirm the population basis and your obligations with counsel.

By [Nilesh Gadekar, Founder](https://districtproof.io/about#founder) · Last reviewed November 4, 2026.

Source checked November 4, 2026 · [U.S. Department of Justice guidance](https://www.ada.gov/resources/small-entity-compliance-guide/).

## What technical standard applies?

The rule specifies [Web Content Accessibility Guidelines (WCAG) 2.1 Level AA](https://www.w3.org/TR/WCAG21/) for covered web content and mobile apps. Documents available through a public website are part of the content to review. The rule also contains exceptions and other provisions that require a careful reading.

## Which date applies?

| Applicable population | Current date |
| --- | --- |
| 50,000 or more | April 26, 2027 |
| Fewer than 50,000 | April 26, 2028 |

The DOJ’s guidance reflects the April 2026 extension. Check the live primary guidance when making a planning or legal decision.

## Use population, not enrollment

A city school district uses the city’s population. A county school district uses the county’s population. An independent school district uses the population estimate in the most recent [Census Small Area Income and Poverty Estimates (SAIPE)](https://www.census.gov/programs-surveys/saipe.html). The DOJ states that a school district is not a special district government for this purpose.

## What should your team do now?

- Identify the entity and applicable population source with counsel
- Inventory documents and key website tasks
- Prioritize active services, forms, and frequently used content
- Review potential exceptions with the people responsible for legal decisions
- Agree on a remediation scope, publishing schedule, and review method
- Keep the delivered and published file versions connected in the evidence record

## Do older documents always qualify for an exception?

No. Date alone is not a determination. The archived-content and preexisting-document exceptions have specific conditions. Documents used to apply for, access, or participate in services receive particular treatment. Read the [exceptions explainer](https://districtproof.io/resources/archived-content-exception-explained) and the primary DOJ guidance.

## What does a backlog report tell you?

It helps estimate the publicly linked documents, page count, and complexity of the work. It does not determine a district’s legal status or provide a full technical audit of every file. [Start with your free PDF Backlog Report](https://districtproof.io/backlog-report).

## Estimate and confirm

[Use the population-based deadline estimator](https://districtproof.io/resources/deadline-calculator) with a population you have verified. Then confirm the applicable date and obligations with counsel. For document work, explore [DistrictProof Docs](https://districtproof.io/solutions/docs).

## Create a planning record your team can revisit

The date is one input to a larger district plan. Keep a record of the entity classification, population source, data year, source link, date checked, and the person responsible for confirming the basis. This makes it easier to revisit the decision when guidance or source data changes. The estimator can apply the population threshold, but it does not establish which population your entity should use.

Do not substitute student enrollment, attendance, or a rough local estimate for the relevant population source. If the district is uncertain whether the city, county, or independent-district basis applies, resolve that question with the people responsible for legal and administrative decisions. Record the decision rather than allowing different departments to plan around different assumptions.

## Build the inventory around public tasks

A website inventory is most useful when it explains why content exists. Start with the things families and community members do: enroll, request a service, find nutrition information, follow transportation instructions, review board material, or contact an office. Connect each task to the pages, documents, forms, and external tools it uses.

A technical crawl helps find publicly linked files, but a departmental conversation adds context. A PDF may be active even if it has an old date. A recently uploaded file may duplicate an existing source. The inventory should separate discovery facts from decisions that need a content owner or counsel.

| Inventory field | How it helps planning |
| --- | --- |
| Public URL and file identifier | Find the exact item and any repeated posting locations. |
| Department and content owner | Route questions to someone who can approve the information. |
| Current use | Understand which service or task depends on the item. |
| Source availability | Decide whether to repair an editable original or an exported file. |
| Document mix | Plan for text, tables, charts, scans, and interactive forms. |
| Version and review state | Keep production, approval, and posting progress distinct. |

## Prioritize a first tranche of work

A plan does not need to begin by treating every document as equally urgent. Discuss active service forms, instructions needed to participate in programs, current notices, and board materials with the responsible teams. Use content importance, actual use, complexity, source availability, and publishing dependencies to shape a first scope.

This is operational prioritization, not an exception determination. A project order does not decide which content the rule covers or whether a particular defense applies. Keep legal review visible as a separate workstream. DistrictProof can provide an inventory and remediation scope while the district makes those decisions with counsel.

Illustrative district scenario

### Two departments, one shared document

A form appears on a district program page and a school office page. The teams first confirm that both locations should serve the same current version. Remediation is then connected to the agreed source and both posting actions. This avoids repairing one edition while a different copy remains in active use.

## Budget for the whole publishing workflow

The effort includes more than editing file tags. Plan for discovery, source retrieval, content clarification, remediation, review, district acceptance, publication, and verification. Some of those activities belong to the district, some may belong to a CMS vendor, and some can be included in a service engagement.

Ask a provider to show where its quoted scope begins and ends. Does it return files only, update editable sources, assist with posting, or verify live versions? Does human review cover the actual task? Are new revisions or packet supplements included? A fixed quote is useful when those assumptions are understandable.

## Set milestones that describe real completion

A milestone should identify its output and review state. “Inventory delivered” means something different from “automated checks passed,” “human review complete,” or “published version verified.” Keep those labels separate in the plan and in any board update. Otherwise a high-level count can make work appear further along than it is.

The evidence record can include filenames, versions, review dates, methods, open findings, district approvals, and public locations. It should also identify scope limits. A result for a selected set of files or pages should not silently become a statement about the entire district website.

## Plan for content published after the project

A one-time backlog project does not cover every later upload. Identify the departments and recurring materials likely to create new work: menus, calendars, board packets, newsletters, forms, and reports. Establish an intake owner and decide when files should be reviewed before publication.

Source templates and short staff guidance can reduce repeated problems. A recurring service can keep the queue and evidence current. DistrictProof [Care](https://districtproof.io/solutions/care) is designed to scope that ongoing routine separately from the initial document project.

## Questions for a district planning meeting

Bring the communications lead, technology owner, board office, purchasing representative, and the person responsible for legal questions as appropriate. The aim is to identify decisions and owners, not to expect one person to settle every issue in a single meeting.

- Which population basis and source have we confirmed?
- Which public tasks and current documents should we inventory first?
- Who owns source retrieval and substantive content decisions?
- Which work requires a website or third-party vendor?
- What evidence will we use to accept work and report progress?
- How will newly published or revised content enter the process?

## Primary references and a practical starting point

Read the [DOJ small entity guide](https://www.ada.gov/resources/small-entity-compliance-guide/) and [DOJ fact sheet](https://www.ada.gov/resources/2024-03-08-web-rule/) for the rule summary and current dates. Use the [Census SAIPE program](https://www.census.gov/programs-surveys/saipe.html) for the independent-district population source and [WCAG 2.1](https://www.w3.org/TR/WCAG21/) for the technical standard.

Then request a [free PDF Backlog Report](https://districtproof.io/backlog-report) to begin sizing the publicly linked document work. The report and a representative sample can support a fixed-quote discussion without requiring the district to guess the entire backlog at the outset.