What WCAG Compliance Actually Requires of K–12 Districts
By Kalin Schoephoerster | KShep Creative
This is the fifth post in a six-part series on WCAG for K–12 districts. Previous posts cover what WCAG is →, what the conformance levels mean →, the difference between WCAG 2.1 and 2.2 →, and the four POUR principles →.
By this point in the series, you have the foundation. You know what WCAG is, what Level AA requires, which version applies to your district, and how the four POUR principles organize the standard. The next question is the most practical one: what does this actually require us to do?
That question has a clear answer — but it's often obscured by misconceptions about scope, timeline, and what "compliance" means in practice. Districts that misunderstand those things either underestimate the work involved or overestimate it, and either mistake gets in the way of making real progress.
This post addresses the practical compliance picture directly: what content is covered, what the timeline looks like, what ongoing conformance actually means, and where to start if your district hasn't yet.
What content ADA Title II actually covers
The first thing most districts underestimate is scope.
Under the updated ADA Title II rule, the requirement applies to websites and mobile apps of public school districts. But "websites and mobile apps" is broader in practice than it sounds. The coverage extends across several content types that districts publish regularly.
Web pages. Every publicly accessible page on the district website is covered — not just the homepage or the pages the district considers important. Board meeting pages, department pages, staff directories, news posts, event calendars, and job listings are all covered.
Documents published online. PDFs, Word documents, Google Docs, and other files linked from the district website are covered. A family handbook published as a PDF is covered. Board meeting minutes posted online are covered. A staff job posting in PDF format is covered. The document doesn't need to be created as a web page to fall under the requirement — if it's accessible from the district's website, it's in scope.
Videos. Any video published on the district website or linked from it is covered — board meeting recordings, instructional videos, event recaps, and communication videos. Captions and audio descriptions are required for video content.
Online forms. Enrollment forms, contact forms, survey tools, and any other interactive form published online are covered. These are often among the highest-stakes content on a district website because families depend on them to complete required processes.
Third-party content the district controls. Embedded tools, calendars, and platforms the district has chosen to use fall under the district's responsibility when they're integrated into district-controlled web presence. Content from platforms the district has no ability to influence or replace has more limited coverage — but the line between what the district does and doesn't control isn't always obvious.
Most districts have significantly more covered content than they initially realize when they start mapping the scope. For more on one of the most common and challenging content types, see PDF Accessibility for K–12 Districts →.
What the compliance timeline looks like
ADA Title II compliance deadlines are phased based on the population the district serves.
In April 2026, the U.S. Department of Justice issued an Interim Final Rule extending both compliance deadlines by one year. Districts serving populations of 50,000 or more now have until April 26, 2027. Districts serving populations under 50,000 and special districts now have until April 26, 2028. The technical standard did not change. WCAG 2.1 Level AA is still the benchmark.
For districts approaching their deadline: the most important thing to understand is that remediating years of accumulated content takes longer than most districts expect. Starting the process of understanding where you stand — through an accessibility audit — well before the deadline is significantly better than starting the remediation itself close to it.
The extension is not a reason to slow down. It's a reason to do this properly: time to build accessibility into content creation rather than bolt it on at the end, time to train the people creating documents, and time to set up vendor contracts that keep new content from creating new problems.
For a full breakdown of the ADA Title II rule and its history, see What K–12 Districts Need to Know About the New Federal Digital Accessibility Rules →.
What ongoing conformance actually means
This is the most important and most frequently misunderstood aspect of WCAG compliance: it is not a finish line.
A district that completes an accessibility audit, remediates the issues found, and then continues publishing content without accessible practices in place will drift out of conformance. Ongoing conformance requires three things working together.
Remediating existing content. The accumulated content on a district website — years of PDFs, videos, pages, and documents — needs to be evaluated and brought into conformance. This is usually the largest and most time-intensive part of the work, and it's where most districts start. Prioritization matters. High-traffic pages, required public information, enrollment materials, and content with safety significance should come first. The goal isn't to fix everything simultaneously — it's to fix the most impactful things first and work systematically from there.
Building accessible creation practices going forward. Every new page, document, or video published needs to meet the standard. Staff who create and publish content need to understand basic accessibility requirements — not at a technical level, but at a practical one. What does an accessible PDF look like? How do you add alt text to an image in a Word document? When does a video need captions? These are learnable skills, and building them into standard workflows prevents the remediation backlog from growing back after it's been cleared.
Monitoring and maintaining. Websites change. Content gets added, updated, and removed. Platforms get upgraded. Accessibility conformance that's accurate today may not be accurate in six months if no one is watching it. Periodic audits, staff training refreshers, and clear ownership of accessibility across departments are what make conformance sustainable rather than a one-time project.
The most common misconceptions about WCAG compliance
These five misconceptions come up consistently in K–12 accessibility conversations. They're worth addressing directly because each one can lead a district to underinvest, delay, or falsely believe they've already done enough.
"An automated scan means we're compliant." Automated accessibility tools catch roughly 30 to 40 percent of WCAG issues. The rest require manual testing — keyboard navigation checks, screen reader evaluation, and human judgment about whether content is genuinely understandable and usable. An automated scan is a useful starting point. It is not a conformance assessment.
"We only need to fix the homepage." The requirement applies to all covered web content — every page, every linked document, every embedded tool. High-traffic pages are the right priority, but the scope isn't limited to the pages the district considers most visible.
"Our website vendor handles this." Website platforms and vendors can support accessible design — but they don't guarantee accessible content. The district is responsible for the content it publishes, regardless of the platform it's published on. A district whose vendor provides an accessible template still needs to publish accessible content within it.
"We passed an audit two years ago, so we're fine." Accessibility conformance is not permanent. Content added after an audit may not be accessible. Platform updates may introduce new issues. Conformance needs to be maintained, not just achieved once.
"We're too small to be a target." ADA Title II applies to all public school districts regardless of size. The compliance timeline is longer for smaller districts, but the requirement is the same. Waiting until the deadline passes is a higher-risk strategy than starting now.
Where to start if your district hasn't begun yet
The compliance picture is clear. The starting point is practical.
Step 1: Understand where you stand. You can't build a remediation plan without a baseline. An accessibility audit evaluates your current content against WCAG Level AA and gives you a prioritized picture of what needs to be addressed and in what order. This is almost always the right first step — not because it's required, but because it makes everything that follows more efficient and more defensible.
Step 2: Prioritize by impact. Start with the content that reaches the most people and carries the most consequence — enrollment forms, family handbooks, board meeting materials, emergency information, staff onboarding resources. Address those before working through lower-traffic content. The goal is to reduce the most significant barriers first.
Step 3: Build the practices that prevent the backlog from growing. Training staff who publish content, building accessibility into document templates, and establishing clear ownership of accessibility across departments all reduce future remediation burden. The goal is making accessible content creation the default — not the exception — so conformance is maintained without requiring a major remediation effort every few years.
What comes next
The final post in this series is a practical WCAG self-assessment checklist — a tool your district can use to start evaluating your own content against the most common and highest-impact WCAG requirements before bringing in outside support.
[A WCAG Self-Assessment Checklist for K–12 Districts → coming soon]
Compliance is a process, not a project
WCAG conformance isn't something a district achieves once and moves on from. It's a commitment to building and maintaining digital content that works for everyone who needs to access it — families navigating enrollment, staff completing required training, community members attending board meetings, and students interacting with district resources.
The districts that handle this well aren't the ones that treat it as a compliance exercise. They're the ones that treat it as an ongoing practice. That shift in framing is what makes the work sustainable.
If your district is ready to understand where it stands and build a realistic plan for getting into conformance, that's exactly what an accessibility audit provides.
Book a free 30-minute intro call →
Or explore accessibility audit and remediation services → to see what a WCAG evaluation looks like in practice.
Kalin Schoephoerster is a CPACC-certified instructional designer and accessibility consultant based in St. Paul, MN. KShep Creative partners with K–12 districts, higher education institutions, and EdTech organizations to develop accessible eLearning, instructor-led training, curriculum, SOPs, and website accessibility audits aligned with WCAG 2.2 and ADA Title II requirements.