Skip to content

ADA Title II Digital Accessibility Reference

This page summarizes the current federal digital accessibility rule and practical steps a District Administrator can help coordinate. It is general information, not legal advice. District counsel should review legal conclusions, policies, contracts, exceptions, and compliance determinations.

Download the schoolboard.net information sheet (PDF)

At a glance

The U.S. Department of Justice's 2024 Title II rule establishes WCAG 2.1 Level A and Level AA as the technical standard for state and local government web content and mobile apps. The rule applies to public school districts and to covered content provided directly or through contractual, licensing, or other arrangements.

Public entity Current compliance date
Population of 50,000 or more April 26, 2027
Population under 50,000 April 26, 2028
Special district government April 26, 2028

Use the correct population measure

The rule does not use student enrollment. For a city school district, use the city population; for a county school district, use the county population; and for an independent school district, use the latest Census Bureau Small Area Income and Poverty Estimates (SAIPE) population estimate. DOJ states that a public school district is not treated as a special district government for this rule.

The compliance dates do not replace existing ADA responsibilities, including effective communication, reasonable modifications, and equal opportunity.

What District Administrators should coordinate

A District Administrator is not expected to make legal determinations alone. Work with district leadership, the accessibility coordinator, communications staff, IT, records staff, procurement, and legal counsel as appropriate.

District-level work should include:

  1. Assign ownership. Identify who coordinates accessibility decisions, remediation, author training, vendor follow-up, and public feedback.
  2. Inventory current digital services. Include district and school websites, board agendas and archives, documents, forms, portals, mobile apps, and vendor platforms.
  3. Prioritize active and essential content. Start with current agendas, enrollment and employment information, emergency information, forms, calendars, policies, and frequently used services.
  4. Use structured HTML when practical. Publish agenda text and other frequently updated information as accessible HTML. Do not assume that a PDF is accessible because it opens or contains selectable text.
  5. Train content authors. Require useful headings, descriptive links, alternative text, accessible tables, sufficient contrast, keyboard-operable content, and meaningful form labels.
  6. Test more than automated scans. Include keyboard use, zoom and reflow, screen-reader review where appropriate, focus visibility, forms, error messages, and document testing.
  7. Include accessibility in procurement. Establish district requirements for evaluating third-party services, known limitations, remediation commitments, update practices, testing, and contract terms before purchase or renewal.
  8. Provide a feedback path. Make it easy to report an accessibility problem and to request an accessible alternative or assistance.
  9. Document decisions and progress. Keep the inventory, testing results, remediation priorities, vendor responses, training, and follow-up current.

Limited exceptions require careful review

DOJ identifies five limited exceptions involving certain archived content, some preexisting conventional electronic documents, some third-party content, certain individualized secured documents, and preexisting social media posts. Each exception has conditions.

Do not assume that all older documents, archives, password-protected content, or third-party material are exempt. Content used to apply for, access, or participate in a current service, program, or activity may require accessibility. Ask district counsel to review fact-specific exception decisions.

Four WCAG principles

  • Perceivable: People can obtain the information, including text alternatives, captions, adaptable structure, and sufficient contrast.
  • Operable: People can use the content with a keyboard, see focus, avoid keyboard traps, and navigate consistently.
  • Understandable: Labels, instructions, navigation, and error messages are clear and predictable.
  • Robust: Semantic HTML and correctly used accessibility information work reliably with browsers and assistive technology.

District responsibility for conformance

Each district is responsible for evaluating its digital content, documents, workflows, and third-party services and for determining its level of conformance. Establish district-controlled review, testing, procurement, remediation, documentation, and legal-review processes. schoolboard.net provides platform features and administrator guidance but does not certify a district's compliance.

schoolboard.net resources

Authoritative references

Check the current rule

Digital accessibility requirements can change. Confirm current DOJ guidance and consult district counsel before adopting deadlines, contract language, policy language, or a formal compliance position.