School district website accessibility reports

Start with the family tasks that must work

Inventory the public district site and each school domain or subdomain before ordering. A single-domain report should not be interpreted as coverage of every school, vendor portal, mobile app, or authenticated student service. Identify who owns each service and how families can request assistance while barriers are addressed.

Prioritize enrollment instructions, accommodation contacts, transportation updates, current board materials, emergency notices, and contact forms. A shared navigation or link-label repair may benefit hundreds of pages; a single inaccessible application form may prevent a family from completing an essential task. Use reach and service impact together.

• Technology staff: shared templates, navigation, embedded tools, and vendor coordination.
• Communications and school offices: headings, meaningful links, image descriptions, and newly published documents.
• Program owners: accessible completion of enrollment, applications, and other multi-step transactions.

Title II timing is not based on student enrollment

The DOJ guidance reviewed September 26, 2026 incorporates the April 2026 interim final rule: April 26, 2027 for public entities with a population of 50,000 or more; April 26, 2028 for smaller public entities and special district governments. School districts are not classified as special district governments for this rule.

DOJ explains that city school districts use city population, county school districts use county population, and independent school districts use the applicable Census Small Area Income and Poverty Estimates population estimate. Do not substitute enrollment for that calculation. Confirm the entity category and deadline with the district’s responsible officials and current DOJ guidance.

The rule’s technical standard is WCAG 2.1 Level AA. Existing duties to provide accessible services do not disappear until the technical deadline. This page is planning information, not a determination of the district’s legal obligations.

What an ADAReporting school report contributes

The automated crawl identifies supported WCAG-rule findings on reachable public HTML pages and separates recommendations from mapped rule failures. It records affected URLs and available element evidence, and groups likely shared-template work while retaining occurrences. An executive summary makes the scope and next actions visible without a compliance score.

Discovered PDF candidates are processed through bounded PDF/UA validation. A machine failure identifies specific conformance checks; it is not proof that the entire document is unusable. Download failures, encrypted files, and resource limits are reported as could not test rather than accessibility failures. Reading order, meaningful alternatives, and practical document usability still require review.

Use the report with your provider: ask for a repair owner, acceptance criteria, a target date, and evidence from retesting. Neither a report nor an automated rescan should be treated as an accessibility certificate.

Make ongoing publishing part of the solution

Before publishing a board packet or school newsletter, start from a structured source document, use real headings and table headers, provide meaningful alternatives, and export a tagged PDF. Check the result rather than assuming the export setting guarantees accessibility.

Create a short intake workflow for staff: identify the service, the audience, the intended publication period, and the owner who can correct the source. Do not assume that every old PDF is exempt, or that a separate HTML summary always replaces an inaccessible document. Applicable exceptions are narrow and context-dependent.

Complete the work automation cannot establish

Test keyboard operation, focus visibility and order, screen-reader announcements, form errors and success messages, zoom and reflow, and actual task completion. Review captions against the audio and check whether important visual information needs description. Exercise interactive states such as expanded menus and validation errors.

Assign this manual work explicitly. Automated findings can help target effort, but absence of detected findings does not establish that a student, parent, employee, or community member can complete the task.