What Is WCAG? A Plain-Language Introduction for K–12 Leaders
By Kalin Schoephoerster | KShep Creative
This is the first post in a six-part series on WCAG for K–12 districts.
If you work in K–12 education, you've almost certainly encountered the acronym WCAG. Maybe it showed up in a vendor contract. Maybe a state guidance document referenced it. Maybe someone on your team mentioned it in a meeting and the conversation moved on before anyone stopped to ask what it actually means.
WCAG gets used as if everyone already knows. Most people don't — or they have just enough understanding to follow along without enough to act on it confidently. That gap is worth closing, because WCAG is no longer a technical detail that only IT departments need to understand. It's the standard behind legal requirements that apply to every public school district in the United States.
This post is for K–12 leaders who want to understand WCAG without wading through technical documentation. No prior background required. By the end, you'll know what WCAG is, where it comes from, what it covers, and why it's showing up in so many K–12 conversations right now.
What WCAG stands for
WCAG stands for Web Content Accessibility Guidelines. It's a set of technical standards for making digital content accessible to people with disabilities — websites, documents, apps, and online tools. It's published and maintained by the World Wide Web Consortium, known as W3C, the international organization responsible for setting web standards broadly.
One thing worth clarifying upfront: WCAG is not a law. It's a technical standard. But it's the technical standard that laws reference when they define what "accessible" means in practice. In the United States, both ADA Title II and Section 508 point to WCAG as the benchmark for digital accessibility. That's why a document produced by an international standards body ends up in K–12 policy conversations — it's the definition the legal requirements are built on.
When a law says your district's website needs to be accessible, WCAG is how you measure whether it is.
Where WCAG comes from and why it exists
WCAG wasn't created as a compliance exercise. It was created because the web was developing new barriers for people with disabilities at the same speed it was creating new possibilities for everyone else.
A screen reader user who couldn't navigate a website because it had no structure. A person who is Deaf who couldn't access video content because there were no captions. A person with low vision who couldn't read text because the contrast between the text and background was too low. These weren't edge cases — they were systematic exclusions built into the way digital content was being created.
W3C developed WCAG to address those barriers in a consistent, documented, testable way. The goal was a standard that anyone building digital content could follow, regardless of the technology they were using.
The standard has evolved over time as the web has evolved:
WCAG 1.0 was published in 1999 — the first attempt at a systematic framework for web accessibility.
WCAG 2.0 followed in 2008 and became the foundation that most current accessibility requirements are built on.
WCAG 2.1 arrived in 2018, expanding the standard to better cover mobile accessibility and the needs of users with cognitive and low vision disabilities.
WCAG 2.2 is the current version, published in October 2023, with additional criteria focused on cognitive disabilities, low vision, and mobile users.
WCAG is a living standard — maintained and updated rather than written once and left. Each version builds on the last rather than replacing it. A closer look at the differences between 2.1 and 2.2, and what they mean for your district, is coming in the third post in this series.
What WCAG actually covers
WCAG covers digital content. Websites, web applications, documents published online, videos, online forms, and mobile apps. It's specifically about the digital experience — not physical accessibility like ramps or parking, and not print materials that aren't published digitally.
The disabilities WCAG addresses fall into four broad categories:
Visual disabilities — people who are blind or have low vision and rely on screen readers, magnification, or high contrast settings to access digital content.
Auditory disabilities — people who are Deaf or hard of hearing and need captions, transcripts, or visual alternatives to audio content.
Motor disabilities — people who can't use a mouse and navigate using a keyboard, switch access, or other assistive input devices.
Cognitive disabilities — people who benefit from clear language, consistent navigation, predictable layouts, and content that doesn't create unnecessary cognitive load.
WCAG doesn't address every possible disability or every possible digital barrier. But it addresses the most significant and most common ones in a systematic, testable way.
One thing worth naming: accessibility improvements benefit more people than those with permanent disabilities. Captions help someone watching a video in a noisy environment. High contrast helps someone reading on a phone in bright sunlight. Clear language helps someone reading in their second language. WCAG sets a floor — and content that meets that floor tends to work better for everyone.
Why K–12 districts are hearing about WCAG right now
WCAG has existed since 1999, but the urgency in K–12 conversations is relatively new. Two developments explain why.
Updated federal regulations. The U.S. Department of Justice finalized updated ADA Title II rules in 2024 requiring public school districts to make their websites and mobile apps conform to WCAG 2.1 Level AA. This is a new, specific, enforceable requirement — not a best practice suggestion or a voluntary commitment. Compliance deadlines are phased based on district size. Larger districts had a deadline of April 24, 2026. Smaller districts and special districts have until April 26, 2027. For a full breakdown of what the rule requires and what your district's timeline looks like, see What K–12 Districts Need to Know About the New Federal Digital Accessibility Rules →.
Vendor accountability. As awareness of these requirements has grown, districts are asking vendors more pointed questions about accessibility. LMS providers, website platforms, and third-party tools are being asked to demonstrate their accessibility conformance — and WCAG is the standard those conversations happen in. A district that understands WCAG is better equipped to evaluate vendor claims, ask for the right documentation, and make informed decisions before purchasing tools.
What WCAG is not
Three quick clarifications that come up often.
WCAG is not a law. It's a technical standard that laws reference. The law requiring your district to act is ADA Title II. WCAG is how you measure whether you're meeting it.
WCAG is not a one-time test you pass. Conformance is ongoing. Every new page, document, or video your district publishes needs to meet the standard. A site that was audited and remediated two years ago may not conform today if content has been added without accessibility in mind.
WCAG is not only for large districts. ADA Title II applies to all public school districts regardless of size. The timeline is longer for smaller districts, but the requirement is the same.
What comes next
Now that you have a foundation for what WCAG is, the next post in this series goes deeper into what WCAG's conformance levels actually mean — specifically what Level A, Level AA, and Level AAA require, and why Level AA is the target for K–12 districts.
WCAG Levels Explained: What Level AA Actually Means for Your District →
Understanding WCAG is the first step
Most K–12 districts aren't starting from zero with accessibility — they have websites, they publish content, they use tools. What many don't have is a clear picture of where they stand relative to the standard they're now required to meet.
Understanding what WCAG is and why it exists is the foundation for that picture. The next step is finding out what your district's content actually looks like against it.
Book a free 30-minute intro call →
Or learn more about accessibility audits and remediation → to see what evaluating your district's content against WCAG actually involves.
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.