By Nilesh Gadekar, Founder · Last reviewed .
How to use this term in a district project
For district planning, keep the legal obligation, technical standard, applicable date, and production project distinct. A provider can support an inventory, remediation, testing, and evidence, but the district and counsel determine how the rule applies to the entity and its content. Use primary guidance when checking the planning basis.
A district example
An administrator asks for a document plan. The team confirms the applicable population and date with the appropriate staff, then scopes the actual files and website tasks.
A useful review question
Who has confirmed our entity and population basis, and where is that decision recorded?
Continue with a practical guide
Explore the related DistrictProof guide or service, or return to the full accessibility glossary. Technical criteria and legal obligations should be checked against the applicable primary references and the agreed review scope.
Connect the rule with a practical district program
ADA Title II concerns state and local government services, programs and activities. The web and mobile application rule adds a named technical standard and applicable dates for covered digital content. A district planning program needs to connect that framework with its actual services, content owners and publishing workflows. Technology staff can identify websites and systems, communications can identify content and public tasks, and purchasing can collect vendor evidence. The district’s legal and records advisers handle the application of the rule and exceptions. A remediation provider supports the defined technical work and its delivery record.
District example: building a first funded project
Imagine a fictional district preparing a document accessibility budget. Its website has current enrollment materials, board packets, archived minutes and department notices. The project begins with an inventory and representative sample, rather than assuming every file requires the same work. Staff identify the owners of active materials, collect available editable sources and ask the appropriate district reviewers about archive decisions. Purchasing uses the resulting scope to request a fixed price and delivery milestones. The first funded project can then name the actual files, required review method and district approvals instead of relying on a general website-wide promise.
Confirm the population basis and date
The DOJ guidance currently lists April 26, 2027 for entities with a population of at least 50,000, and April 26, 2028 for smaller entities. School district planning uses the applicable resident population rather than student enrollment. Independent school districts and districts operated by a city or county have different population sources in the guidance. Record the source and the responsible district reviewer before using a date in a board plan. The DistrictProof estimator uses a population entered by the visitor; it does not look up or independently verify that population.
Assign decisions before the production queue grows
The district should identify who approves document meaning, who chooses what remains public, who publishes returned files and who responds to accessibility requests. An accessibility reviewer should not have to invent a missing policy explanation or decide whether an official record may be deleted. Put those questions into an owned issue process. The website vendor may need to fix shared components while district authors improve source documents. Keep both streams connected to the same public tasks so a repaired document does not remain behind a confusing link or an unusable interaction.
Report progress through specific evidence
For board reporting, distinguish inventory, triage, remediation, human review, district acceptance and publication verification. A count of received files describes a different state from a count of reviewed and posted versions. Use a dated manifest so staff can trace the public file back to the work that was delivered. Plan ongoing intake for new notices, forms and board materials after the first backlog project. A useful agreement identifies the technical outputs, allowances, turnaround and correction process, while the district maintains its own policy and legal decisions. The result is a program that staff can operate and explain as content continues to change.