Digital Accessibility for US School and College Websites: ADA & Section 508 Obligations 2026

What US schools must do under the ADA and Section 508

Public sector educational institutions in the United States — including K-12 districts, state colleges and universities, and other state and local government entities — face a clear federal compliance deadline. Under the Department of Justice's ADA Title II Final Rule on Web and Mobile App Accessibility (issued April 2024 and codified at 28 CFR Part 35), state and local government entities — including public schools, community colleges, and public universities — must ensure that their web content and mobile apps comply with WCAG 2.1 Level AA. Larger entities (50,000+ population) face a compliance deadline of April 24, 2026; smaller entities and special-purpose districts have until April 26, 2027.

Federal agencies and federally funded programs have been bound by Section 508 of the Rehabilitation Act since 1998 (revised 2017), which incorporates WCAG 2.0 AA by reference. Educational institutions receiving federal funding — most colleges and universities through Title IV — must ensure that procurement of electronic and information technology meets Section 508 standards.

Title II of the ADA has applied to public educational institutions since 1990. Title III applies to private institutions deemed "places of public accommodation," which the DOJ has confirmed extends to private colleges and universities. An inaccessible website constitutes a prima facie failure of these duties, regardless of institutional size, and the Office for Civil Rights (OCR) at the US Department of Education actively investigates accessibility complaints against funded institutions.

The business case is as direct as the legal one. According to Skolbot's mystery shopping audit (2025, 80 institutions), schools without an AI chatbot record an average bounce rate of 68%. An inaccessible website compounds this: approximately 15% of visitors with disabilities cannot navigate a non-compliant site effectively, abandoning before submitting an inquiry. At typical post-secondary conversion rates, that translates to dozens — sometimes hundreds — of lost applications per year.

The technical standard underpinning all of this is WCAG 2.1 AA, with WCAG 2.2 (published October 2023) increasingly cited by accessibility auditors and OCR investigators. WCAG 2.1 AA is the standard explicitly referenced in the DOJ's April 2024 Final Rule.

The legal exposure for non-compliant institutions

OCR investigations are the most common enforcement pathway for K-12 districts and colleges. OCR has resolved hundreds of accessibility complaints through corrective action agreements that typically require: a comprehensive accessibility audit, public posting of an accessibility statement, remediation timelines, mandatory staff training, and ongoing monitoring. While OCR rarely imposes financial penalties directly, the cost of a corrective action agreement — staff time, third-party audit fees, software remediation — routinely exceeds $100,000 for a mid-sized institution.

Private litigation is the second major exposure. Title III ADA lawsuits against private colleges and universities have grown materially since 2018. Plaintiffs typically seek injunctive relief and attorneys' fees; class actions can drive settlements into seven figures. California's Unruh Civil Rights Act provides additional state-law exposure with statutory damages of $4,000 per violation, and similar state-level frameworks operate in New York, Massachusetts, and other jurisdictions.

Under the new DOJ Title II Final Rule, public institutions face a compliance deadline rather than a litigation-driven enforcement model. April 24, 2026 (or April 26, 2027 for smaller entities) is the federal compliance trigger; failure to meet WCAG 2.1 AA conformance by that date creates direct DOJ enforcement risk in addition to OCR exposure.

Public institutions registered with accreditors (SACSCOC, HLC, MSCHE, WASC, NEASC, NWCCU regional accreditors, plus programmatic accreditors) face an additional risk: accessibility non-compliance can surface in accreditation review and trigger conditions on continued accreditation status.

College-listed institutions in particular should note that accessibility failures increasingly appear in student satisfaction surveys, College Scorecard data, and Niche reviews — influencing prospective applicants' choices before they even reach your website.

The four WCAG principles — what they mean for a school website

WCAG 2.1 is organized around four principles, abbreviated as POUR: Perceivable, Operable, Understandable, and Robust. Each maps to concrete failures that appear repeatedly in higher education audits.

At Level AA, WCAG 2.1 adds requirements that are particularly relevant for schools: minimum color contrast ratios (4.5:1 for standard text, 3:1 for large text), no loss of functionality on 400% zoom, and captions for all pre-recorded video. WCAG 2.2 adds nine new success criteria, including more stringent focus appearance requirements and a ban on dragging movements as the only means of interaction — both areas where existing school websites commonly fail.

Publishing your accessibility statement

While the DOJ Title II Final Rule does not require a formal accessibility statement in the way that some other jurisdictions do, posting one is strongly recommended best practice and is required under many state and institutional policies. A clear statement communicates your conformance status, lists known issues with target fix dates, identifies any third-party content not covered, and provides a contact mechanism for users to report problems or request accessible alternatives.

The W3C provides templates and guidance for accessibility statements that meet international and US best practices. For federally funded entities subject to Section 508, the Section 508.gov accessibility statement guidance provides a template aligned with federal requirements.

The statement should be published on a dedicated page linked prominently from the footer of every page on the site. It should be updated whenever a new audit is conducted or a known issue is resolved. Statements that are out of date — listing issues already fixed, or omitting newly discovered ones — undermine your defensible compliance position and can be cited adversely in OCR or DOJ investigations.

Institutions that use third-party platforms — a common scenario in admissions, where Common App, Coalition App, or vendor-hosted application portals sit on separate domains — must assess those tools separately. If the portal is procured by the institution and presented to users as part of the application process, the institution bears responsibility for its accessibility under both ADA Title II/III and (for federally funded procurement) Section 508. Contractual conformance requirements and a Voluntary Product Accessibility Template (VPAT) or Accessibility Conformance Report (ACR) should be standard procurement deliverables.

10 priority checks for your school's website

If your institution has not undergone a formal accessibility audit, these ten checks address the most frequently cited failures in the higher education sector and the most common findings in OCR resolution agreements.

1. Color contrast — Test all text against its background using a tool such as WebAIM's Contrast Checker. Standard body text must achieve a ratio of at least 4.5:1; headings above 18pt require 3:1.
2. Image alt text — Every informative image must have a descriptive alt attribute. Decorative images should have an empty alt (alt="") so screen readers skip them.
3. Form labels — Each form field must have a programmatically associated <label> element. Placeholder text alone does not meet WCAG 2.1 Success Criterion 1.3.1.
4. Video captions — All pre-recorded video (campus tour recordings, program teasers, testimonials, lecture recordings) must have accurate captions. Auto-generated captions from YouTube or Zoom require review and correction. This is also an OCR-cited failure under Section 504 and Title II for K-12 districts.
5. Keyboard navigation — Navigate your entire site using only the Tab, Enter, and arrow keys. Every interactive element must be reachable and operable without a mouse.
6. Skip navigation link — A "Skip to main content" link should appear as the first focusable element on every page, allowing keyboard and screen reader users to bypass repeated navigation.
7. PDF accessibility — Course catalogs, viewbooks, and policy documents published as PDFs must be tagged, have a logical reading order, and include alt text for any images. Adobe Acrobat's accessibility checker is a reasonable starting point. PDF inaccessibility is a leading category in OCR complaints.
8. Focus indicators — The keyboard focus state must be clearly visible at all times. CSS that removes the default browser outline without providing a high-contrast replacement is a common, easily fixed failure.
9. Error identification — When a form is submitted with errors, each problem must be identified by name and described in text. Relying solely on color to indicate an error fails WCAG 2.1 Success Criterion 1.4.1.
10. Responsive and zoom behavior — At 400% zoom, all content and functionality must remain available without horizontal scrolling (except for data tables, which are exempt). Test on both desktop and mobile.

These checks are achievable without specialist tools. For a more thorough audit, institutions should engage an accessibility consultant (IAAP-certified CPACC or WAS practitioners are the recognized US credential) using a WCAG conformance evaluation methodology (WCAG-EM) that covers representative pages from each template type in use.

For further context on how data collected through accessible web forms must be handled, see the GDPR Guide for Student Data and Protecting Prospect Data Under Privacy Law. If your institution is also evaluating AI tools for admissions, AI Bias in Student Admissions covers the risk classification obligations that apply to automated chatbots and screening systems.

FAQ

Are private colleges and universities covered by the new DOJ Title II Final Rule?

The DOJ April 2024 Title II Final Rule applies to state and local government entities, which covers public K-12 districts, public community colleges, and public universities. Private institutions are not directly bound by the Title II rule but remain bound by ADA Title III as places of public accommodation, by Section 504 of the Rehabilitation Act if they receive federal financial assistance (which most do via Title IV), and by Section 508 for federally funded procurement. The substantive standard — WCAG 2.1 AA — is the same in practice. Private institutions facing Title III lawsuits routinely face WCAG 2.1 AA as the de facto compliance benchmark in settlement.

What is an accessibility statement and where should it appear?

An accessibility statement is a published page on your website that describes your conformance status, lists known accessibility issues with target fix dates, explains what users can do if they encounter a problem, and names a contact for accessibility-related requests. While not formally mandated by federal rules in all cases, it is widely recommended best practice and is required by many state and institutional policies. It must be linked from the footer of every page. It should be reviewed and updated whenever your site changes significantly or a new audit is completed. A statement that lists no issues is almost always inaccurate and may itself attract regulatory or litigation attention.

Does WCAG apply to third-party tools like our admissions portal?

Under both ADA Title II/III and Section 504, institutions cannot simply disclaim responsibility for inaccessible third-party tools they have procured and present to users as part of their service. If a prospective student encounters an inaccessible Common App-integrated portal, a CRM-powered contact form (Slate, Salesforce Education Cloud, TargetX), or a virtual campus visit platform that your institution has embedded or linked to, you must assess whether reasonable accommodations are possible or whether an accessible alternative exists. When procuring new platforms, accessibility conformance should be a contractual requirement — ask vendors for a Voluntary Product Accessibility Template (VPAT) or an Accessibility Conformance Report (ACR) referencing WCAG 2.1 AA.

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.1 (published June 2018) added 17 success criteria to WCAG 2.0, with a focus on mobile accessibility and users with cognitive or low-vision disabilities. It is the standard explicitly referenced in the DOJ April 2024 Title II Final Rule. WCAG 2.2 (published October 2023) adds 9 further criteria, including clearer requirements around focus appearance, target size for interactive elements, and authentication that does not require cognitive tests. WCAG 2.2 is backwards-compatible — a site conforming to 2.2 AA also conforms to 2.1 AA. While 2.1 remains the enforceable baseline for federally regulated entities, accessibility auditors increasingly benchmark against 2.2, and the W3C has deprecated 2.0's Success Criterion 4.1.1 in the 2.2 version.

Where should we start if our website has never had an accessibility audit?

Begin with a baseline automated scan using a tool such as axe DevTools or WAVE — these identify roughly 30–40% of WCAG failures without any specialist knowledge. Review your most visited page templates: homepage, program pages, contact and application forms, and any video content. Run through the 10 priority checks listed above. Then commission a manual audit from an IAAP-certified accessibility specialist covering a representative sample of pages, including those with interactive elements. Use the audit findings to populate your accessibility statement, prioritize fixes in your next development sprint, and establish a quarterly review cycle. Public institutions should specifically scope their audit and remediation against the April 2026 (or April 2027) compliance deadline under the DOJ Title II Final Rule.