School website accessibility: what actually breaks

Ask an AI assistant “who builds websites for private schools that parents can actually navigate,” and right now it names Finalsite — every time, across every major engine we probe. Ask a narrower question, “our school website is failing accessibility, who can rebuild it properly,” and the field splits between Finalsite, an accessibility consultancy, and a specialty vendor. What neither prompt returns is a plain-language answer for the person who actually owns the problem: a head of school with a five-year-old WordPress site, no in-house developer, and a nagging feeling the site wouldn’t survive a real audit.

That feeling is usually correct. We ran AI audits on two dozen school sites this week — day schools, charter schools, Montessori programs — and the pattern was consistent: solid intentions, thin execution. Here’s what actually breaks, and what fixes it.

What does “failing accessibility” look like on a real school site?

Not a lawsuit-triggering disaster, usually — smaller and more common than that. Low-contrast text over a hero photo that reads fine to a sighted designer at their desk and fails outright for a parent with low vision. Buttons and dropdown menus that only respond to a mouse, so a keyboard-only or switch-device user can’t get past the main nav. Photos of the science fair with no alt text, so a screen reader announces “image” and moves on — losing the one thing that might have shown a family what campus life is actually like. Heading levels used for visual size instead of structure, so the page reads as a wall of text to any tool trying to parse it.

None of these show up in a quick glance at the homepage. All of them show up the moment a real visitor — or a crawler — tries to use the site instead of just looking at it.

Why does this cost more than a compliance headache?

Two audiences read your site the same way a screen reader does: assistive technology, and AI assistants. When a page’s structure is a mess of non-semantic divs and unlabeled images, a screen reader user and Claude or ChatGPT hit the identical wall — no reliable way to tell what the page is actually saying. That’s why the two problems travel together in the data: schools that score low on accessibility in our audits also score low on AI-readiness, almost without exception. Fix the structure once, and both audiences benefit — the family touring your campus by screen reader, and the parent asking an AI assistant to shortlist three schools nearby.

Right now, when a parent asks an AI assistant which schools are worth touring, most schools simply aren’t part of the answer. Not because the school is a bad fit — because the site never told the assistant anything concrete enough to repeat.

What actually fixes it, beyond “hire someone with WCAG in their bio”?

Four things, in the order we’d prioritize them for a school specifically:

• Contrast and text sizing that pass automated checks and look right to a sighted visitor — these are not in tension once a designer builds with both constraints from the start, rather than retrofitting them.
• Full keyboard navigation on every menu, form, and modal — the enrollment inquiry form is worthless if a keyboard-only visitor can’t submit it.
• Real alt text and heading structure, written by a person who has seen the actual photos and pages, not auto-generated filler that technically satisfies a linter and says nothing.
• A content structure AI assistants can quote — plain-language program descriptions, a clear admissions FAQ, and schema markup that states what the school teaches, where, and for what ages, so an assistant has something specific to repeat back.

None of this requires rebuilding your entire brand. It requires building the next version with accessibility as a starting constraint instead of an afterthought — which, done right, takes about the same time as building it without.

Is this a one-time fix or an ongoing commitment?

Both, and that’s the part most vendors skip. A compliant launch that degrades the first time front-office staff add a low-contrast flyer image or skip alt text on next year’s staff photos isn’t really compliant — it’s compliant until Tuesday. The fix that holds is structural: templates and components that make the accessible choice the default choice, so a non-technical staff member adding a calendar event can’t accidentally break contrast or heading order. That’s the difference between “we passed an audit once” and “we stay compliant without thinking about it.”

What should a school actually do this month?

Run a real check before assuming either way. Our free audit scores performance, design, SEO, AI-readiness, and lead capture on your current site in a couple of minutes — no obligation, and the report is yours either way. If accessibility and AI-readiness come back weak (they usually travel together), that’s the fix worth prioritizing first, because it’s the one that helps a family touring by screen reader and a parent asking an AI assistant at the same time.

See how we approach school website builds in detail — enrollment funnels, staff-editable calendars, and accessibility built in from the first template, not bolted on after a complaint.