Web accessibility means building a website so that people with disabilities can use it as fully as everyone else. That includes a student who navigates entirely by keyboard, a parent who relies on a screen reader, a teacher with low vision who zooms the page to 200 percent, and a child who cannot process flashing animation. When a site is accessible, none of those people hit a wall. When it is not, they get locked out of things the rest of us take for granted, like checking a grade, reading a closure notice, or registering for a class.
For schools this is not a nice-to-have. It is a legal obligation, a practical one, and frankly a moral one. A public school website is a public service, and a public service that only works for some of the public is not finished. This guide explains the standards that define accessibility, how compliance actually works, and the handful of fixes that deliver most of the benefit.
The three names you will keep hearing
Accessibility law and standards in the United States revolve around three things, and it helps to know how they fit together.
WCAG is the technical rulebook. The Web Content Accessibility Guidelines, published by the World Wide Web Consortium, are the international standard for what makes digital content accessible. They are organized around four principles, easy to remember as POUR: content must be Perceivable, Operable, Understandable, and Robust. WCAG sets three conformance levels, A, AA, and AAA. Almost every legal and institutional requirement targets level AA, which is the realistic, comprehensive middle tier. WCAG 2.1 is the version most rules point to today, and WCAG 2.2 adds a small set of newer criteria on top of it.
The ADA is the law. The Americans with Disabilities Act does not mention websites by name, because it predates the modern web, but courts and the Department of Justice have consistently treated websites as covered. In 2024 the DOJ finalized a rule under Title II that explicitly requires state and local government entities, which includes public schools and districts, to meet WCAG 2.1 level AA. Larger public entities face compliance deadlines in 2026, smaller ones in 2027. If you run a public school site, this is the deadline on your calendar.
Section 508 is the federal procurement standard. It requires federal agencies and many organizations that receive federal funding to make electronic information accessible, and it also points to WCAG level AA. For schools, Section 508 most often shows up indirectly, through the edtech vendors and learning platforms you buy, which are expected to document their own conformance.
The simple way to hold all of this in your head: the ADA and Section 508 say you must be accessible, and WCAG defines what accessible means.
How conformance actually works
Accessibility is not a badge you earn once and hang on the wall. It is a property of every page, every PDF, every embedded video, and every form on your site, and it can break the moment someone uploads a new document. Compliance is a practice, not a finish line.
In practice, conformance is measured against the individual WCAG success criteria. Each one is a specific, testable statement, such as "images have text alternatives" or "color is not the only way information is conveyed." A page conforms at level AA when it satisfies all the A and AA criteria that apply to it. There is no partial credit at the page level: one missing form label can make a form unusable for a screen reader user even if everything else is perfect.
This is why serious organizations publish an accessibility statement. It is a public page that names the standard you are targeting, describes the known limitations, and gives people a way to report a barrier and get help quickly. A good statement is not legal cover. It is an honest status report and a door people can knock on, and the fact that you maintain one signals that accessibility is an ongoing commitment rather than a one-time audit.
The fixes that matter most
Accessibility can feel overwhelming because WCAG has dozens of criteria. The reassuring truth is that a small number of issues cause the majority of real-world barriers. Year after year, automated surveys of the web's most popular sites find the same culprits at the top of the list. If you fix these, you have done most of the work.
Text alternatives for images. Every meaningful image needs alt text that describes what it conveys. A photo of the principal needs a name. A chart needs its takeaway in words. Purely decorative images should be marked so screen readers skip them rather than announce "image, image, image."
Real contrast. Light gray text on a white background looks elegant and reads terribly. WCAG asks for a contrast ratio of at least 4.5 to 1 for normal text. This single fix helps an enormous number of users, including anyone reading on a phone in sunlight.
Labels on form fields. A search box, a login, a registration form: every field needs a programmatic label, not just a placeholder that vanishes when you start typing. Without labels, a screen reader user cannot tell what to type where.
Keyboard operability. Try using your site without a mouse. Tab through it. Can you reach every link, open every menu, submit every form, and see where the focus is? Many users navigate this way out of necessity, and a menu that only opens on hover quietly excludes them.
Descriptive links and headings. Links that all say "click here" are useless to someone scanning a page by link list. Headings that are styled to look like headings but are not actually marked up as headings break the outline that screen reader users rely on to move around.
Captions and document accessibility. Video needs captions. PDFs need to be tagged and readable rather than scanned images of text. Schools generate an avalanche of PDFs, and untagged ones are one of the most common hidden barriers in education.
Misconceptions worth clearing up
A few myths cause schools to either panic or stall, so let us address them directly.
"An automated checker will tell me if I am compliant." It will not, and believing this is the single most expensive mistake. Automated tools are genuinely useful and you should run them, but they reliably catch only a fraction of WCAG criteria, commonly estimated at roughly a third to a half. They can tell you an image lacks alt text. They cannot tell you whether the alt text is meaningful, whether the page makes sense when read aloud in order, or whether a keyboard user can actually complete a task. Real conformance requires manual testing, ideally including people who use assistive technology.
"We need a separate accessible version of the site." Almost never. A parallel "text-only" site tends to lag behind the real one, miss content, and signal second-class treatment. Modern accessibility means one site that works for everyone, not a side door.
"An overlay widget will fix it." Those one-line scripts that promise instant compliance, the little accessibility button in the corner, are widely criticized by disabled users and accessibility experts. They can interfere with the assistive technology people already have configured, and they do not address the underlying code. Several have drawn lawsuits rather than prevented them. There is no shortcut script for accessibility.
"This is only for a tiny group." Roughly one in four adults in the United States lives with a disability. Add temporary and situational limits, a broken arm, a bright screen, a noisy room, an aging parent, and accessible design quietly improves the experience for nearly everyone. Captions help the student in a quiet library. Good contrast helps everyone outdoors. This is the curb-cut effect: build the ramp for some, and a lot more people roll through it.
Where to start, and where to get help
If you are responsible for a school site and do not know your status, do not aim for perfection on day one. Start with a baseline. Run a free automated scan, then test the most important journeys by hand, your homepage, your enrollment form, your closure notice, using only a keyboard and then a screen reader. Fix the high-impact issues first: contrast, alt text, form labels, headings, and your PDF pipeline.
For authoritative resources, the W3C Web Accessibility Initiative publishes the WCAG standard along with plain-language explanations and a quick-start checklist for each criterion. The ADA's own guidance describes the Title II rule and its deadlines. And vendors you buy from should be able to hand you an accessibility conformance report describing how their product measures up.
Accessibility is not a project you complete and forget. It is a habit, the same way proofreading or backing up files is a habit. The schools that do it well are not the ones with the biggest budgets. They are the ones who treat every new page as something a real person, with a real disability, will try to use tomorrow morning. Build for that person, and you have built for everyone.