ADA Title II Digital Accessibility for Public Schools

What Public Schools Need to Know

The U.S. Department of Justice has adopted a rule requiring state and local government entities to make their web content and mobile applications conform to a specific technical standard by a specific date. Public school districts are state and local government entities, so the rule applies to them.

For a district, the rule reaches further than the district website. It reaches individual school sites, parent and student portals, online forms, the documents posted through those systems, instructional content delivered through district platforms, videos, and mobile apps. It reaches content provided through platforms the district licenses as well as systems the district builds.

The compliance dates are April 26, 2027 and April 26, 2028, depending on the district's population figure. Both dates reflect a one-year extension the Department of Justice adopted in April 2026. This page explains which date applies to a district, what the standard requires, what content is covered, where the limited exceptions apply, and what a district can sensibly do between now and then.

Are Public School Districts Covered

Yes. Title II of the Americans with Disabilities Act applies to public entities, and public school districts are public entities. The Department of Justice's guidance for entities preparing to comply addresses school districts directly, including how a district determines its compliance date and how the rule applies to course content.

Coverage does not depend on district size, on whether the district receives particular federal funding, or on whether the district employs technology staff. A district with four hundred students and a district with four hundred thousand are both covered. Size determines only which of the two dates applies.

Public charter schools that are organized as public entities under state law are likewise covered as public entities. Charter arrangements vary considerably from state to state, and a charter operator should determine its own status under state law rather than assume.

This rule sits alongside, and does not replace, the obligations districts already have. The Individuals with Disabilities Education Act governs individualized services for eligible students through the IEP process. Section 504 of the Rehabilitation Act prohibits disability discrimination by recipients of federal financial assistance and supports individual accommodations and plans. The Title II web rule is different in character: it is a systemic obligation about the accessibility of the district's digital content for everyone, not an individualized entitlement triggered by a particular student's needs. A district can be fully compliant with IDEA for every eligible student and still not meet this rule.

Which Deadline Applies to a School District

The rule defines total population rather than leaving districts to estimate it, and school districts are addressed specifically.

An independent school district, or an instrumentality of one, uses the population estimate for the district calculated by the Census Bureau in the most recent Small Area Income and Poverty Estimates. This is a population figure for the geographic area the district covers. It is not the district's student enrollment, and it is not the population of a nearby city unless the district's own boundaries happen to match it.

A school district that is part of a city or county government rather than an independent district uses that government's population. The Department's compliance guide puts it simply: a city school district uses the population of the city, and a county school district uses the population of the county.

Special district governments are assigned the later date, but districts should not assume they fall into that category. The rule's definition of special district government expressly excludes independent school districts. A school district is therefore not a special district government for purposes of this rule simply because it is a district, and most school districts will determine their date from a population figure rather than defaulting to 2028.

A district that is uncertain which branch of the definition applies to it should resolve that question early, because it determines whether the district has until 2027 or 2028, and because the difference is a full school year of preparation time.

The 2027 and 2028 Deadlines

Public entity, other than a special district government, with a total population of 50,000 or more: April 26, 2027

Public entity with a total population of less than 50,000: April 26, 2028

Any public entity that is a special district government: April 26, 2028

These dates are the extended dates adopted in April 2026 and currently written into the regulation. They replaced the original dates of April 24, 2026 and April 26, 2027. A district still planning against an April 2026 date is planning against a date that no longer appears in the rule.

What Standard Applies

The rule requires conformance with the Level A and Level AA success criteria and conformance requirements of WCAG 2.1, the Web Content Accessibility Guidelines published by the W3C as a Recommendation on 5 June 2018. Level AAA is not required.

WCAG 2.2 is a newer W3C Recommendation and is the version the W3C encourages organizations to use. It did not supersede WCAG 2.1, and it is backward compatible, so content meeting WCAG 2.2 Level AA also meets WCAG 2.1 Level AA. For a district, WCAG 2.1 Level AA is the regulatory requirement and WCAG 2.2 Level AA is a reasonable design and procurement target that satisfies it. Districts should not write WCAG 3 into specifications or contracts; it remains an early working draft and is not a standard.

What School Content Can Be Covered

The rule covers web content and mobile applications a public entity provides or makes available, directly or through contractual, licensing, or other arrangements. Applied to a school district, that framing reaches most of what a district publishes digitally.

Content categories that clearly fall within the rule include district websites and individual school websites; parent and student portals; online enrollment, registration, permission, and payment forms; conventional electronic documents such as PDFs, word processing files, presentations, and spreadsheets made available through those systems; audio and video content delivered through district web properties; district mobile apps; and content delivered through platforms the district licenses for instruction or administration.

The named platforms a district uses are examples of how the rule applies rather than categories the rule itself lists. The Department's rule speaks in terms of web content and mobile apps provided directly or through contractual arrangements; it does not enumerate specific products. The analysis for any particular system is the same: if a district makes content available through it, the content is within scope.

Course content deserves specific mention. The Department's guidance states that course content has no exception and must meet WCAG 2.1 Level AA, and that the exception for preexisting conventional electronic documents does not rescue educational content in current use. Instructional materials are not a lower-priority category under this rule.

Teacher-Created Content

This is the part of the rule districts find hardest, and it is worth stating carefully.

The rule applies to web content and mobile app content the district provides or makes available. Material a teacher creates and posts through district systems, such as a document uploaded to a learning management system, a slide deck shared through a district platform, or a page on a school site, is content the district makes available and is within scope. The Department's guidance to entities states that teacher-posted links and course materials must comply.

That is not the same as saying every file a teacher has ever created is automatically covered in every context. The analysis follows the content into the district's digital systems. A worksheet printed and handed out in a classroom is not web content. The same worksheet posted to a course site for students to download is.

The practical implication for districts is not that teachers must become accessibility specialists. It is that the district needs accessible templates, default settings that produce accessible output, clear and short guidance for the handful of things that matter most, and training that reaches the people actually creating content. Districts that approach this as an individual compliance burden on thousands of staff generally fail. Districts that approach it as a tooling, template, and training problem generally do better.

PDFs and Electronic Documents

Documents are usually the largest category of covered content in a district and the least well understood.

An accessible document generally has real heading structure rather than text that merely looks like headings, so a reader can navigate between sections; a logical reading order so that a screen reader presents content in the order it was meant to be read, which matters most in documents with columns, text boxes, or complex layouts; meaningful alternative text on images and charts that convey information, with decorative images marked as decorative; properly structured tables with identified header rows rather than layout grids; link text that describes the destination rather than a bare address or the words click here; and sufficient contrast between text and background.

Documents exported to PDF carry over the structure of the source file, which means accessibility work is far cheaper in the original Word, Google Docs, or presentation file than in the exported PDF. A tagged PDF produced from a well-structured source is usually straightforward; remediating an untagged PDF after the fact is usually not.

This is an overview rather than a document accessibility tutorial. For more detailed guidance, see Accessible Documents.

LMS and Digital Instruction

Learning management systems and instructional platforms sit at the center of a district's digital footprint, and they raise two distinct questions.

The first is whether the platform itself is accessible: whether a student can navigate it by keyboard, whether a screen reader announces its controls correctly, whether its assessment tools are usable with assistive technology. That is largely a procurement and vendor question, and the district should ask for current conformance information and verify it.

The second is whether the content placed inside the platform is accessible, and that is a district question regardless of how good the platform is. A fully accessible learning management system will faithfully deliver an inaccessible scanned PDF. Common platforms used in K-12 settings include Canvas, Schoology, Google Classroom, Blackboard, and Moodle; naming them here is descriptive of the K-12 market rather than an endorsement of any product, and the same analysis applies to any platform a district uses.

Videos and Multimedia

Video and audio content in a district context includes recorded instruction, board meetings, announcements, and promotional material.

Under WCAG 2.1 Level AA, prerecorded video with audio requires captions and audio description of visual information that is not otherwise conveyed; prerecorded audio-only content requires a transcript; and live video with audio requires captions. Media players also need to be operable by keyboard and usable with assistive technology, which is a common failure point in embedded players.

Automatic captions generated by a platform are a starting point rather than a finished product. Their accuracy varies with audio quality, speaker accents, and subject-specific vocabulary, and student names and technical terms are frequently wrong. Captions that misstate the content do not provide equivalent access.

Vendor and Third-Party Platforms

Districts buy a great deal of their digital footprint, and it is a common assumption that buying transfers the accessibility obligation. It does not.

Under the rule, content provided through a contractual, licensing, or other arrangement is treated as the district's own. Content posted by unaffiliated members of the public, such as a comment on a public page, falls within an exception; a licensed instructional platform does not. The Department's guidance to entities is explicit that using an outside service does not remove the obligation, and it advises reviewing contracts, requesting detailed accessibility information, and considering warranty language addressing the technical standard.

What the rule does not do is allocate responsibility or cost between a district and its vendors. That allocation is a matter of contract. A district whose vendor will not remediate is still the district with the obligation, which is why the terms agreed at purchase and renewal matter more than any other single lever a district has.

Where a platform cannot be made accessible in time, a district should document the limitation, pursue remediation with the vendor, and provide an accessible alternative means for students and families to obtain the same information or complete the same task. That is a mitigation, not a substitute for conformance.

Procurement

Procurement is where districts can change their long-term position most efficiently, because every contract signed without accessibility terms locks in the status quo for the length of that contract.

Ask for a current accessibility conformance report for the specific version being purchased, and read it critically. These reports are vendor self-assessments prepared using a standard template; they vary widely in quality, they may describe an older version, and a report that shows many criteria as supports with explanatory notes may be describing significant gaps. The existence of a report does not mean a product is accessible.

Require accessibility language in the contract itself rather than relying on a marketing claim, including the applicable standard and conformance level, the vendor's obligation to remediate defects, and timelines for doing so.

Test high-risk and high-use systems before purchase where possible, particularly anything students must use to complete required work or that families must use to access a service.

Document remediation commitments and track them at renewal, because renewal is the next realistic opportunity to change the terms.

For more detailed guidance on conformance reports, see VPAT and Accessibility Conformance Reports. For the full purchasing process, from requirements through contracts, acceptance, and renewal, see Accessible Procurement.

Exceptions and Legacy Content

The rule contains five exceptions, and districts should read them narrowly because each has conditions that are easy to fail.

Archived web content is excepted only if it was created before the compliance date or reproduces earlier paper or physical media, is retained exclusively for reference, research, or recordkeeping, is not altered or updated after archiving, and is stored in a dedicated area clearly identified as archived. Old content sitting in an unmaintained folder does not qualify.

Preexisting conventional electronic documents posted before the compliance date are excepted unless they are currently used to apply for, access, or participate in a service, program, or activity. For a district this is the crucial qualifier: an enrollment form, a handbook families still rely on, or instructional material still assigned remains in scope regardless of when it was posted.

Content posted by third parties not acting under an arrangement with the district is excepted. Individualized password-protected documents about a specific person, such as an individual student record in a conventional document format, are excepted. Social media posts created before the compliance date are excepted; later posts are not.

A conforming alternate version may be used where a technical or legal limitation prevents the primary content from being made accessible, and a district may show that a particular nonconformance is so minor that it does not affect a person's ability to use the content with substantially equivalent ease, though the burden of showing that rests with the district.

What Districts Should Do Now

The rule prescribes no compliance process. The sequence below reflects how this work is usually approached in school systems and is offered as practical implementation guidance rather than as a requirement of the regulation.

First, inventory the district's digital footprint: the district site, every school site, portals, forms, licensed platforms, and mobile apps. Most districts find systems they had forgotten, including sites built for past initiatives and tools purchased by individual schools.

Second, identify the highest-priority systems and content: what families must use to enroll, pay, communicate, or obtain services, and what students must use to complete required work.

Third, establish ownership. Name someone accountable for the program and assign owners to individual systems.

Fourth, train the staff who create content, with short role-specific guidance rather than a general accessibility course.

Fifth, fix templates and defaults. Correcting a site template, a document template, or a course shell resolves the same defect everywhere it would otherwise be reproduced.

Sixth, update procurement language and apply it at the next renewal.

Seventh, test using both automated and manual methods, including keyboard-only navigation and screen reader checks on the systems that matter most.

Eighth, remediate according to the priority order rather than working through content in the order it was found.

Ninth, monitor continuously, because districts publish new content every day and a site that conforms in spring will not stay that way by itself.

Tenth, be ready before the deadline rather than on it, which in practice means starting the procurement and template work at least a full school year ahead.

Role-Based Preparation

Administrators and superintendents set the expectation that this is a district program with an owner, a budget, and a schedule, rather than a technology department side project. The decisions that matter most at this level are ownership, funding, and procurement policy.

Technology staff maintain the systems inventory, handle platform-level and template-level defects, run automated monitoring, coordinate vendor remediation, and support testing.

Teachers work within templates and defaults that the district provides. The highest-value practices are using built-in heading styles, writing meaningful alternative text, checking that captions are accurate rather than merely present, using descriptive link text, and avoiding scanned images of text.

Instructional technology and curriculum staff decide what materials and platforms are adopted, which makes them one of the most consequential groups in the process. Accessibility belongs in adoption criteria alongside pedagogy and cost.

Procurement and business officials control contract terms, conformance report requests, remediation commitments, and renewal timing.

Communications and web staff own the most visible content: the district and school sites, announcements, board materials, and video. Template quality and publishing practice have outsized effects here.

Frequently Asked Questions

Are documents teachers post covered? Content a teacher makes available through district web systems or platforms is within scope. The Department's guidance states that teacher-posted links and course materials must comply. A document that exists only on paper in a classroom is not web content.

Are old documents exempt? Only if they are not currently used to apply for, access, or participate in a service, program, or activity. Active enrollment forms, handbooks, and assigned instructional materials are not exempt regardless of age.

Do Google Docs and Slides need to be accessible? If they are made available through district systems, yes. The file format does not determine coverage; how the content is provided does.

Does content inside a learning management system matter? Yes. The platform and the content inside it are separate questions, and the district is responsible for the content it places there.

What about vendor software? Content provided through a contractual or licensing arrangement is treated as the district's own for purposes of the rule.

Is WCAG 2.2 required? No. The rule incorporates WCAG 2.1 Level A and AA. Meeting WCAG 2.2 also meets WCAG 2.1, and it is a reasonable target, but it is not the requirement.

What deadline applies to my district? An independent school district uses the Census Bureau's Small Area Income and Poverty Estimates population figure for the district; a city or county school district uses that government's population. A figure of 50,000 or more means April 26, 2027, and a figure under 50,000 means April 26, 2028.

Are there fines for each inaccessible file? No provision of this rule establishes per-document fines. Title II is enforced through federal complaint investigation, voluntary compliance agreements, referral to the Attorney General, and private litigation, with remedies that include injunctive relief, damages in appropriate cases, and attorney's fees.

Related AssistiveTechnology.org Resources

For the full rule in its state and local government context, including entity coverage, exceptions, and enforcement, see ADA Title II Digital Accessibility for State and Local Governments. For a general orientation to digital accessibility standards and practices, see Digital Accessibility. For assistive technology under IDEA and the IEP process, see Education, IDEA & IEPs. For the postsecondary transition, see Assistive Technology for College and Postsecondary Education. For technology that supports reading and writing access in instruction, see Reading Assistive Technology and Writing Assistive Technology. For communication access in the classroom, see Communication & AAC. For what WCAG is and how conformance levels work, see WCAG Overview. For how accessibility is evaluated in practice, see Accessibility Testing and Evaluation. For further reading across topics, see Resources.

Request accessibility services

Primary Sources

28 CFR part 35, subpart H, Web and Mobile Accessibility, sections 35.200 through 35.205, and the definitions of total population and special district government in section 35.104.

Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities, 89 FR 31337, April 24, 2024, as amended by AG Order No. 6742-2026, 91 FR 20902, April 20, 2026.

U.S. Department of Justice, ADA.gov: Small Entity Compliance Guide and First Steps Toward Complying with the Title II Web and Mobile Application Accessibility Rule, which address school district compliance dates and course content.

W3C Web Accessibility Initiative, WCAG 2 Overview, for the status of WCAG 2.1 and WCAG 2.2 and the development status of WCAG 3.

Last Regulatory Review

Last regulatory review: September 20, 2026. On that date the compliance dates, the incorporated technical standard, the school district population methodology, the exceptions, and the enforcement framework described on this page were verified against the current text of 28 CFR part 35 and current Department of Justice guidance.

Update History

September 18, 2026 - Page created. Current Department of Justice compliance dates of April 26, 2027 and April 26, 2028 verified against the current Code of Federal Regulations text. WCAG 2.1 Level A and AA confirmed as the standard incorporated by the rule. Independent school district population methodology confirmed as the Census Bureau's Small Area Income and Poverty Estimates figure, and independent school districts confirmed to be excluded from the definition of special district government.

About This Page

This page provides general educational information about digital accessibility requirements as they apply to public school districts in the United States. It is prepared by The Accessibility Clinic Inc. as educational information only. It is not legal advice, and it does not guarantee that any specific website, application, document, or platform meets a particular standard or legal requirement. Districts should evaluate their own obligations in light of their specific circumstances and consult qualified counsel when needed. Regulations and standards change; the last regulatory review date above indicates when the regulatory statements on this page were most recently verified against primary sources.