School Website Accessibility Guide for Private School Heads of School

If you are a Head of School running a private K-12 serving 260 students, you are probably not losing sleep over web accessibility. You should be. Web accessibility has moved from an IT footnote to a compliance risk with real teeth, and most private schools are still underinvested. The April 24, 2026 DOJ deadline for Title II entities has raised enforcement visibility across the sector, and legal counsel for independent schools now treat WCAG 2.1 AA as the operational standard for every school website, regardless of religious affiliation or size.

This guide is for a Head of School making decisions about a 260-student college-prep K-12 private school with a marketing budget in the $30,000-$75,000 range. It covers the legal frameworks that actually apply to your school, the technical standards you have to meet, the lawsuits and settlements shaping the enforcement landscape, the audit process, the CMS-specific challenges, the cost of remediation, and the governance model that keeps the site compliant after launch. It is written to give you the analysis you need to talk to counsel, the board, and your marketing and IT teams with confidence.

Which Accessibility Laws Apply to Private K-12 Schools?

Three federal laws govern private school website accessibility: ADA Title III, Section 504 of the Rehabilitation Act, and the 2024 DOJ Title II final rule. Depending on your state, additional state civil rights laws may raise the bar further.

ADA Title III: Private Schools as Public Accommodations

Title III of the Americans with Disabilities Act prohibits discrimination in places of public accommodation. The DOJ and a consistent line of federal courts treat private K-12 schools as places of public accommodation, regardless of tuition level or religious affiliation. The practical consequence: your website must be navigable and usable by individuals with visual, auditory, motor, or cognitive impairments, even without any federal funding.

Section 504: The Federal Funding Trigger

Section 504 of the Rehabilitation Act applies to any program or activity receiving federal financial assistance. For private schools, the triggers are often indirect. Any of the following can subject your entire digital infrastructure to Section 504 accessibility obligations.

• Participation in the National School Lunch Program
• Receipt of IDEA (Individuals with Disabilities Education Act) funding for special education
• E-rate program discounts for telecommunications and internet
• PPP loans, emergency federal relief, or any pandemic-era federal support
• Federal research grants

If your school has accepted any of the above, Section 504 compliance is immediate, not a future consideration. A single federal dollar is enough.

The 2024 DOJ Title II Final Rule

On April 24, 2024, the U.S. Department of Justice published a final rule under Title II of the ADA establishing WCAG 2.1 Level AA as the technical standard for web and mobile digital accessibility for state and local government entities, including public school districts. Private schools are not directly covered by Title II, but the rule is widely viewed as the federal government's definitive statement on what "accessible" means under the ADA generally. Legal analysis from JD Supra and other legal publications has pointed to Title II as the operational benchmark courts are likely to apply to Title III claims against private entities.

The DOJ compliance deadlines are April 24, 2026 for public entities serving populations of 50,000 or more, and April 26, 2027 for smaller jurisdictions. Private schools should plan against the earlier date for risk management purposes.

Religious Exemption: Narrower Than You Think

Title III provides an exemption for religious organizations and schools controlled by them. That exemption does not apply to Section 504. If your faith-based school accepts any federal assistance, you are fully subject to WCAG 2.1 AA regardless of religious status. State civil rights laws frequently do not mirror the federal religious exemption either. Treat the exemption as a narrow shield rather than a full defense.

What Does WCAG 2.1 AA Actually Require?

WCAG 2.1 Level AA is organized around four principles (Perceivable, Operable, Understandable, Robust) and roughly 50 success criteria. The practical requirements for a school website come down to a manageable list of design and development disciplines.

Perceivable

Every non-text element needs a text alternative. Photos need descriptive alt text (the photo of the biology lab is "two students in goggles and lab coats using a microscope," not "DSC_0042"). Videos need synchronized captions and a transcript. Text and images of text must meet a minimum color contrast ratio of 4.5:1 against their background (3:1 for large text). Content must work when zoomed to 200% without loss of functionality.

Operable

Every interactive element must be reachable and operable via keyboard alone. The primary school-website failure here is mega-menus that only open on mouseover, locking out keyboard and assistive-technology users. Focus indicators (the outline that appears as you tab through elements) must remain visible; removing them for aesthetic reasons is one of the most common compliance failures and one of the easiest to spot in an audit. Skip-to-main-content links should be present on every page.

Understandable

Form fields need visible, permanent labels, not placeholder text that disappears when the user types. Error messages must identify where the error is in both text and a non-color indicator ("Please enter a valid email address in the Email field" rather than a red border alone). Page language must be declared in the HTML.

Robust

The page markup must be valid and semantic enough that assistive technologies can reliably parse it. This is where the heading hierarchy matters: H1 for the page title, H2 for main sections, H3 for subsections, with no heading levels skipped. It is also where developers often cut corners; clean markup is the foundation for everything else.

What Lawsuits and Settlements Have Hit Schools Recently?

Web accessibility litigation against educational institutions has risen substantially since 2020. The cases that have settled publicly tend to share common failure patterns: missing alt text, inaccessible PDFs, videos without captions, forms without proper labels, and sliders or modal dialogs that are unreachable via keyboard. Many of the high-profile cases involve private colleges and universities, but the legal reasoning transfers directly to private K-12 institutions.

A few enforcement trends are worth noting. First, PDFs are heavily represented in complaints. A school with a handbook, a tuition schedule, and a summer reading list as PDFs that are image-only or not tagged for screen readers is accumulating risk with every published file. Second, third-party embedded content (calendar widgets, course catalogs, donation forms) is not a defense. If it is embedded on your site, you are responsible for its accessibility. Third, settlements increasingly include not just remediation requirements but also mandated accessibility statements, staff training, and multi-year monitoring.

How Does a Private School Run an Accessibility Audit?

A defensible accessibility audit combines automated scanning, manual testing, assistive technology review, and prioritized remediation. Automated tools catch roughly 30-50% of WCAG issues; the rest require manual testing.

Phase 1: Automated Baseline

Run an automated scan on the top 20-30 pages by traffic using one or more of the following tools:

• WAVE from WebAIM, free browser extension
• axe DevTools free tier in Chrome DevTools
• Lighthouse built into Chrome DevTools
• Pope Tech for institution-wide automated scanning

Export the results. Categorize violations by WCAG success criterion and by page importance.

Phase 2: Manual Keyboard and Screen Reader Testing

An automated scan misses issues with focus order, logical heading structure, meaningful link text, and the semantic correctness of dynamic content. Manual testing closes that gap. Run a full keyboard-only pass through the admissions funnel (inquiry, tour request, application). Test the homepage, tuition page, and a representative program page using NVDA (free on Windows) or VoiceOver (built into macOS and iOS). Have a team member who has never used assistive tech before try to complete a tour request without a mouse; the friction surfaces quickly.

Phase 3: PDF and Third-Party Content Review

List every PDF on the site and test each for screen reader accessibility. Most PDFs uploaded from Word or Pages without remediation will fail. The quickest fix is often to convert the content to a native HTML page. Where PDFs remain, they need to be tagged, have a logical reading order, and include alt text for any embedded images.

Phase 4: Prioritized Remediation Plan

Triage findings by impact and effort. The priority order for most school sites is:

• Homepage, admissions funnel, tuition, and financial aid page fixes (high impact, often medium effort)
• Navigation menu and primary forms (high impact, high effort, but essential)
• Faculty directory, program pages, and events (medium impact)
• Archived news, blog, and legacy content (low impact; often merge or remove rather than remediate)
• PDFs (high impact for any file with current relevance; remove or rebuild the rest)

Phase 5: Ongoing Governance

Accessibility is not a one-time project. Build ongoing checks into content governance: a required alt text field in the CMS, monthly spot checks on new content, quarterly automated scans, and annual manual audits. Without governance, remediation debt accumulates again within 12-18 months.

Which CMS Platforms Handle Accessibility Well?

Different CMS platforms come with different accessibility defaults. The platform matters, but staff training matters more.

Industry-Specific Platforms

Finalsite and Blackbaud both ship school-oriented templates that are built with accessibility in mind, which gives new launches a head start on WCAG conformance. The limiting factor on both platforms is what happens after launch. Staff adding pages, uploading PDFs, and embedding third-party widgets can introduce accessibility debt faster than any template can prevent. The platform choice buys you a starting line, not a finish line.

WordPress

WordPress accessibility depends almost entirely on the theme and plugins, which is a harder problem than it sounds. The default themes are not WCAG-ready, and the plugin ecosystem regularly introduces accessibility debt through sliders, modal popups, popup form builders, and page builders that generate non-semantic markup. Every plugin update is a potential regression. A WordPress site can be made compliant, but it demands ongoing governance and a willingness to say no to the plugins your staff wants to install, which is a harder sell than most admissions offices expect.

Joomla

Joomla is the strongest open-source option for schools that prioritize accessibility without committing to an industry-specific platform price tag. Accessibility is built into Joomla's core rather than bolted on through plugins. The default Cassiopeia template ships with semantic HTML5, WAI-ARIA landmarks, skip links, and keyboard-accessible navigation out of the box. The core editor includes an accessibility checker that flags issues before content goes live.

Joomla's access control system is also genuinely granular, which matters for schools where a dozen staff members across admissions, advancement, athletics, and academics all push content to the same site. You can restrict who can publish, who can only draft, and who can touch the accessibility-sensitive elements like navigation menus and forms.

The trade-off is that Joomla rewards an agency partnership more than WordPress does. If your school has no development support, WordPress has a larger DIY ecosystem. If your school has agency support, Joomla gives you stronger accessibility defaults with less ongoing risk.

Squarespace

Squarespace has improved its accessibility defaults in recent years and ships templates with reasonable semantic structure. The trade-off is remediation flexibility. When an audit flags a specific issue, your options are limited to what Squarespace's template system allows. Staff still need to handle alt text, heading structure, and link labels on every page they publish

Wix

Wix has made a visible push on accessibility, including an Accessibility Wizard that flags common issues on existing sites. It helps, but it does not replace manual review. Custom components and third-party app integrations on Wix still introduce accessibility issues that the Wizard does not catch.

Overlay and Widget Solutions

Tools like AccessiBe, UserWay, and similar "accessibility overlays" promise a quick fix. The Overlay Fact Sheet, signed by hundreds of accessibility researchers, developers, and users of assistive technology, specifically warns that overlays can introduce new accessibility problems while masking existing ones, and that they do not bring a non-compliant site into WCAG or ADA conformance. Legal complaints against overlay-equipped sites continue to be filed and settled, reinforcing the position that an overlay on its own is not a defense. Overlays can be part of a remediation toolkit for temporary coverage, but they are not the strategy.

How Much Does Accessibility Remediation Cost?

Remediation costs vary with the state of the existing site. For a mid-sized private school with 260 students, realistic budget ranges are:

• $5,000-$15,000 for a baseline audit and quick-fix remediation on a reasonably modern CMS
• $15,000-$35,000 for a full audit, prioritized remediation, and published accessibility statement on a site with moderate debt
• $35,000-$75,000+ for full remediation on a site with heavy PDF debt, legacy content, and structural CMS issues

Ongoing compliance costs typically run $2,000-$8,000 annually for monitoring tools, occasional consulting, and staff training. Compared to the cost of a demand letter, settlement, and forced remediation under a consent decree, this is cheap insurance.

What Should a School Accessibility Statement Include?

An accessibility statement is both a legal shield and a trust signal. It should be linked from every page, usually in the footer, and should include:

• A commitment to conforming to WCAG 2.1 Level AA
• A description of current conformance status (conformant, partially conformant, or non-conformant, with specifics)
• A clear contact method for accessibility issues (email and phone)
• The tools and testing methods used to assess accessibility
• A summary of known accessibility issues and the remediation timeline
• The date the statement was last updated

Publishing an accessibility statement does not create liability; failing to publish one creates reputational and legal risk. Examples and templates are available from W3C's WAI initiative.

Practical Application: A 260-Student K-12 Compliance Project

Consider a private college-preparatory school with 260 students, tuition of $20,000, a marketing budget of $54,000, and participation in the National School Lunch Program. The school's website was last redesigned in 2019, and no accessibility audit has been conducted.

The Head of School commissions an initial audit in May. Automated scans of the top 30 pages identify 412 critical WCAG 2.1 AA violations, heavily concentrated in missing alt text, keyboard-inaccessible navigation, insufficient color contrast on donor and faith pages, and unlabeled form inputs. A manual review surfaces 27 additional issues not caught by automation, including a tuition table that is an image rather than structured HTML and a virtual tour with no transcript or captions.

Phase 1 remediation (June-July) focuses on the homepage, admissions funnel, and tuition page: accessible navigation, alt text, color contrast, form labels, and a fully rebuilt tuition page. Phase 2 (August-September) addresses faculty pages, program pages, and PDF remediation. Phase 3 (October-December) handles the parent portal integrations and establishes ongoing governance through quarterly automated scans and CMS training for all content editors. Total first-year cost: approximately $27,000 in external remediation, $4,500 in tooling and training, and roughly 80 hours of internal staff time.

By the April 2026 deadline, the site passes WCAG 2.1 AA on all top-30 pages, has a published accessibility statement with quarterly updates, and has established a two-person accessibility review process for any new content. The Head of School briefs the board once, answers zero litigation letters, and protects the school from a common avoidable risk.

Treat Accessibility as an Operational Discipline, Not a Project

Website accessibility is no longer a niche technical concern; it is a civil rights compliance area with real litigation risk for private K-12 schools. The combination of ADA Title III, Section 504 for any federally assisted school, and the 2024 DOJ Title II rule collectively raise the operational standard to WCAG 2.1 AA for almost every private school in the country. Schools that treat accessibility as a one-time project keep accumulating debt; schools that treat it as an operational discipline stay compliant.

If you want a second set of eyes on your current accessibility posture, a budget estimate for remediation on your specific CMS, or a template for an accessibility statement that your counsel will approve, schedule a conversation. A short call now costs less than a demand letter later.

Frequently Asked Questions