Back to School, Nine Months to the Deadline: A School Website Accessibility Checklist

If you run communications for a public school or district in the United States, the new school year that starts in a few weeks is not just the start of a school year. It is the last full academic year you have before a federal accessibility deadline lands.

The Department of Justice’s Title II web rule requires public entities to make their websites and mobile apps conform to WCAG 2.1 Level AA. Larger entities — those serving populations of 50,000 or more — were required to comply by April 24, 2026. Smaller entities and special district governments have until April 26, 2027. Which date applies to a school district generally depends on the population of the area it serves, so a district serving a small town is on the 2027 clock while a big-city district was already due last spring. If you are not certain which category you fall into, that is a question for your counsel, not for a blog post. (Nothing here is legal advice.)

Either way, the practical situation is the same for most district communications staff: you have one school year, no budget line for this, no developer on staff, and a website that hundreds of people publish to. Here is how to spend that year well.

Why school websites fail, specifically

School sites do not fail for exotic technical reasons. They fail because of how they are built and who publishes to them.

Every school in the district has a page. Every teacher has a page. The athletic department posts schedules, the PTA posts flyers, the business office posts board packets, food services posts menus, and the front office posts the bell schedule. None of those people are web professionals, none of them received accessibility training, and all of them are publishing under deadline pressure using whatever tool made it fastest.

The result is remarkably consistent from district to district. It is not broken code. It is thousands of documents and images that nobody can read unless they can see them.

The seven things to fix, in order of who gets hurt

I have ordered these by impact on a real family trying to get information, not by how hard they are.

1. The PDF problem

This is the big one, and it is not close. Lunch menus, school calendars, permission slips, registration packets, bus routes, board meeting minutes, athletic physicals, the student handbook, the newsletter — on most district sites, the actual information lives in PDFs rather than on web pages.

Two things go wrong. First, many of these are scans. Somebody printed the lunch menu, signed it or stamped it, ran it through the copier, and uploaded the resulting image. There is no text in that file at all. A blind parent’s screen reader announces nothing. Second, even PDFs generated digitally are usually exported by printing to PDF, which strips out heading structure, table headers, and the reading order, so the file is technically readable but practically a jumble.

What to do this year: stop uploading scans, without exception. If a document must be scanned, it needs to be replaced by the digital original. Then take your ten most-downloaded PDFs — your web host or analytics can tell you which — and republish that content as ordinary web pages instead of attachments. A lunch menu as an HTML table beats a lunch menu as a PDF for every single person, including sighted parents checking on a phone in a parking lot. For documents that genuinely must stay as files, author them in Word using real heading styles, add alt text to images, mark table header rows, set the document language, run the built-in Accessibility Checker, and then export using the accessibility export option rather than printing to PDF.

Do not try to remediate the whole library. Access is wildly concentrated. Fixing twenty documents will cover most of what anyone actually opens.

2. Flyers posted as images

This one is nearly as common and much easier to fix. Someone designs a flyer for the book fair, the fundraiser, or picture day in Canva or Publisher, exports it as a JPEG, and posts the image. Every word on that flyer — the date, the time, the cost, the location, the deadline — exists only as pixels.

A screen reader user gets nothing. Someone who zooms in gets a blurry mess, because images of text do not scale the way real text does. Someone on a slow connection gets a slow page. And the content is invisible to search, so a parent googling “picture day” on your site finds nothing.

What to do: post the details as text on the page, and use the flyer image as a visual accompaniment with alt text describing it briefly. Same information, same design, one extra paragraph of typing. This is the single highest-value habit change you can teach your building-level publishers.

3. Closure and emergency announcements

When you post a snow day, a lockdown notice, a late start, or a water main break, that information is urgent and it needs to reach everyone. On many school sites, the alert banner is a bright colored bar injected into the top of the page by JavaScript — which means a screen reader user who has already started reading the page may never be told it appeared.

Check three things. Does the alert have enough color contrast to be readable, or is it white text on a light school-color background? Is the alert reachable and readable in a logical order, near the top of the page rather than buried in the markup at the bottom? And if the banner appears dynamically, is it announced? A parent should not have to discover a closure notice by accident.

Also check that the alert is not communicated by color alone. “The red banner means closure” fails for anyone who cannot see red.

4. Video without captions

Board meetings, superintendent messages, virtual open houses, graduation streams, athletic broadcasts, and recorded lessons. Uncaptioned video is a straightforward exclusion of deaf and hard-of-hearing families and students, and school video is the kind of content where auto-generated captions perform worst, because the vocabulary is full of staff names, school names, acronyms, and local place names.

What to do: treat automatic captions as a first draft, not a deliverable. Someone in the office reviews and corrects them before the video is published, focusing on names and acronyms. For long recordings like board meetings, post an agenda-linked summary or transcript so people can find the part they need without scrubbing through two hours of video. And if a video is required viewing — a mandatory training, a required orientation — missing captions should block publication, not go on a to-do list.

5. Staff directories and contact forms

The staff directory is one of the most-used pages on a school site, and it is often a wide table of names, roles, buildings, and email addresses built without header cells, so a screen reader reads it as an undifferentiated stream of text. If your directory is a table, it needs real header rows and columns so each cell is announced with what it means.

Contact and request forms have a related problem: fields labeled only by grey placeholder text that vanishes when you start typing, required fields marked with a red asterisk and nothing else, and error messages that appear visually but are never announced. When a form fails, the family cannot reach the school. That is a bigger deal than a styling bug.

6. Third-party embeds you did not build

Lunch payment portals, tuition and fee payment, athletic schedule systems, online registration, transportation lookup, the LMS login, calendar widgets, and enrollment forms. Districts run on vendor systems, and those systems are frequently the least accessible part of the site.

You cannot fix a vendor’s code. You can do three things. Ask each vendor for their accessibility conformance report and actually test the embedded product yourself rather than filing the document. Put accessibility conformance into your next contract renewal and RFP, which is the only lever that reliably moves vendors. And in the meantime, publish a clearly visible alternative route — a phone number, an email, a paper form available at the front office — so a family blocked by an inaccessible portal can still register their child.

That alternative needs to be genuinely responsive, not theoretical. “Call the office” is only an accommodation if someone answers.

7. School colors and contrast

Districts brand their sites in school colors, and school colors were chosen for jerseys and gym walls, not for reading. Gold text on white, light blue on grey, or a navy-on-black footer all fail readability thresholds that people with low vision depend on.

You do not have to abandon the brand. You need a darker variant of the school color for text and buttons, and enough contrast between text and background. A free contrast checker will tell you in seconds whether a pair passes. While you are there, confirm the keyboard focus outline is still visible — the ring that shows where you are when tabbing through a page. Designers frequently remove it because it looks untidy, which makes the site unusable for anyone navigating without a mouse.

A realistic plan for the school year

You are not going to fix everything, so sequence it.

August and September: Stop the bleeding. Send one short guidance note to everyone with publishing access covering three rules: no scanned PDFs, no flyers posted as image-only, and always use the heading styles instead of just making text big and bold. Three rules is something people will actually remember. Everything published from that point forward stops adding to the pile.

October through December: Fix the top twenty. Pull your most-visited pages and most-downloaded documents and work through only those. Republish the highest-traffic PDFs as web pages. Fix the staff directory table and the main contact form. Run a contrast check on the theme and get the school colors corrected once, centrally.

January through March: Vendors and video. Request conformance documentation from every third-party system on the site, test the important ones yourself, and get accessibility language into any contract coming up for renewal. Establish the caption review habit for board meetings and district announcements.

April: Re-check, and document what you did. A written record of your accessibility efforts and your remediation plan matters, both for your obligations and for the practical reality that this work is never finished.

One thing not to do

Do not buy an accessibility overlay widget — the JavaScript products that promise instant compliance from a single line of code. They do not fix inaccessible PDFs, they do not caption your board meetings, they do not add alt text to flyers, and they do not make a vendor’s registration portal work. What they do is add a visible accessibility badge to a site whose actual barriers are untouched, which is not a good position to be in. The money is better spent on the twenty documents.

The honest summary

A school district website is not hard to make accessible in a technical sense. It is hard because the content is produced by hundreds of people with no training and no review step, and because most of the important information is trapped in files rather than published as web pages.

The deadline is a forcing function, but the reason to do it is more ordinary than that. Somewhere in your district there is a parent who cannot read the lunch menu, a student who cannot follow the board meeting, and a family who cannot complete registration online. They have been working around your website for years. This is the year to stop making them.

We’re building a simple accessibility checker for non-developers — no DevTools, no jargon. Join our waitlist to get early access.