Federal Digital Accessibility Rules for Colleges: The Complete Guide and Tracker 

Updated Oct. 18, 2026. This guide explains the law for a general audience and isn't legal advice. Confirm how it applies to your institution with counsel.

For the first time, federal regulations set a specific technical standard for the websites, apps and online course materials of public colleges and universities: WCAG 2.1 Level AA. In 2026 the deadlines moved. The Justice Department pushed the ADA Title II dates back a year in April, the Department of Health and Human Services followed for its Section 504 rule in May, and the National Federation of the Blind sued both agencies to undo the delays.

This guide covers every federal rule that applies to higher education, what each requires, what counts as an exception, how enforcement is working in 2026, and a step-by-step plan. A tracker of every development is below, and we update it as things change. Free Excel and Word templates are at the end.

Where things stand

Two points matter more than the dates. First, the underlying obligation to give people with disabilities equal access is already in force under the ADA and Section 504; the 2024 rules added a specific technical standard and a deadline. Second, the extensions are being challenged in court, so the earlier dates could come back.

The ADA Title II web rule, in detail

Title II of the Americans with Disabilities Act covers state and local governments, which includes public universities, state college systems and community colleges. The 2024 rule (28 CFR part 35, subpart H) is the most detailed federal accessibility requirement higher education has faced.

What it covers

• Web content: everything on public websites, subdomains, microsites and portals, including text, images, documents, audio, video and forms.
• Mobile apps the institution provides or makes available.
• Content provided through others. Content delivered "through contractual, licensing, or other arrangements" is covered, according to ADA.gov. That brings in learning management systems, online course platforms, registration and payment systems, admissions and housing portals, library databases, and vendor-built microsites.
• Course materials. Content inside password-protected course sites is covered when it's part of the institution's programs. The exceptions below are narrow and rarely cover current course materials.

The standard

Web content and mobile apps must conform to WCAG 2.1 Level A and Level AA: 50 success criteria covering text alternatives, captions, keyboard access, color contrast, structure, forms, focus and more. Level AAA is not required. An institution may use other designs or technologies ("equivalent facilitation") only if they provide substantially equivalent or greater accessibility and usability.

Which date applies

The compliance date depends on the population of the government the institution belongs to, from 2020 Census data, not on enrollment:

• Population 50,000 or more: April 26, 2027. A state university is generally measured by its state's population, so most fall here.
• Under 50,000, and special district governments: April 26, 2028. Some community college districts are organized as special districts. Check yours with counsel; United Educators and others advise confirming the date before planning.

The five exceptions, and their limits

Each exception has conditions, and all must be met. Even when content is excepted, the institution must still provide access when someone with a disability needs it, through effective communication and reasonable modifications.

1. Archived web content. Only if it was created before the compliance date (or reproduces older paper or physical media), is kept only for reference, research or recordkeeping, is stored in a clearly identified archive area, and hasn't been changed since. Updating it, or using it to deliver a current service, ends the exception.
2. Preexisting conventional electronic documents. PDFs, word processing files, presentations and spreadsheets available before the compliance date, unless they're currently used to apply for, access or take part in a program or service. A 2019 syllabus in an archive may qualify; an application form or a document assigned in a current course does not.
3. Third-party content. Content posted by people not acting for the institution (for example, members of the public on a message board). Content from vendors and contractors is not excepted, and neither is content the institution posts itself.
4. Individualized, password-protected documents. A PDF, word processing file, presentation or spreadsheet about a specific person, property or account, secured by a password, such as a student's bill. HTML pages don't qualify.
5. Preexisting social media posts made before the compliance date.

Conforming alternate versions

A separate accessible version is allowed only where a technical or legal limitation prevents making the original content accessible. An inaccessible main page with an "accessible version" link is not a substitute.

Fundamental alteration and undue burden

An institution doesn't have to take an action it can show would fundamentally alter a program or impose undue financial and administrative burdens. The regulation sets conditions (28 CFR 35.204):

• The decision must be made by the head of the public entity or a designee, after considering all resources available for funding and operating the program.
• It must come with a written statement of the reasons.
• The institution must still take any other action that would ensure access to the maximum extent possible.

Our template pack includes a determination record built around these requirements.

Minor shortfalls

The rule says an entity isn't in violation if it can show a failure to conform is so minor that it doesn't affect a person with a disability's ability to use the content in the same way. ADA.gov's example is a 4.45:1 contrast ratio where 4.5:1 is required. This can't be used to avoid trying to meet the standard, and it doesn't excuse barriers such as a form that takes a screen reader user far longer to complete.

Section 504 and the Department of Education

Section 504 of the Rehabilitation Act bars disability discrimination by any recipient of federal financial assistance. That covers public and private colleges that take part in federal student aid programs. The Department of Education's Section 504 rules don't set a web standard, but its Office for Civil Rights (OCR) has long treated inaccessible websites and course technology as discrimination, and its resolution agreements with institutions typically require an accessibility policy, a coordinator, audits and remediation deadlines.

OCR's capacity has shrunk. Seven of its 12 regional offices closed in 2025, the complaint backlog grew past 25,000, and a GAO review found that about 90 percent of complaints resolved between March and September 2025 were dismissed rather than investigated, The 19th reported. That reduces federal investigations, not institutions' obligations: students can still file complaints with OCR and DOJ, and can sue under the ADA and Section 504.

The HHS Section 504 rule

HHS's 2024 Section 504 rule (45 CFR part 84) also adopts WCAG 2.1 AA for web content and mobile apps, for programs that receive HHS funding. Covered recipients include HHS-funded colleges, universities and research institutions, as well as hospitals and health systems, according to Duane Morris. For many research universities and academic medical centers, this rule applies alongside Title II.

The deadlines are now May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for smaller ones. Separately, the Texas v. Kennedy litigation by a group of states challenges parts of the broader Section 504 rule, according to DREDF; the web accessibility standard has remained in effect.

Private colleges: ADA Title III

Private colleges are "public accommodations" under Title III of the ADA. DOJ has no technical regulation for their websites, but its 2022 guidance says the ADA applies to web content and that WCAG and the Section 508 Standards are helpful guides. Private institutions are also covered by Section 504 through federal student aid. In practice, WCAG 2.1 AA is the benchmark in lawsuits and settlements, so private institutions should plan as if the Title II standard applies.

Section 508 and procurement

Section 508 applies to federal agencies, not directly to colleges. Its influence on campus is through procurement: vendors document accessibility in an Accessibility Conformance Report (ACR), usually on the Information Technology Industry Council's VPAT template. An ACR is the vendor's own claim. Treat it as a starting point, test high-impact products yourself, and write WCAG 2.1 AA, remediation timelines and remedies into contracts. Section508.gov explains how to read an ACR critically.

WCAG 2.1 versus 2.2

The federal rules require WCAG 2.1. The W3C published WCAG 2.2 in October 2023 with nine additional success criteria, including focus not obscured, minimum target size, dragging alternatives and accessible authentication. Content that meets 2.2 AA also meets 2.1 AA except for 4.1.1 Parsing, which 2.2 made obsolete. Many institutions now set WCAG 2.2 AA as their internal target so they are ready for future rules.

State laws

Several states set their own standards. Colorado's HB21-1110, for example, requires state and local governments, including public colleges, to meet WCAG 2.1 AA, and allows people to sue. Illinois, California, Texas and others have their own accessibility laws and procurement rules. Check your state's requirements; they may be stricter or earlier than federal rules.

A step-by-step compliance plan

1. Governance (now). Name an executive sponsor and a digital accessibility coordinator. Form a working group with IT, communications, academic affairs and teaching support, procurement, disability services, the library and general counsel. Adopt a policy (our template is a start).

2. Confirm what applies. Determine which rules cover you and which date applies: Title II population group, HHS funding, state law. Our toolkit's "Which rules apply" tab walks through it.

3. Inventory. List websites, subdomains, apps, portals, forms, the LMS, video platforms, document libraries and every vendor platform students use. Note owners and traffic.

4. Prioritize. Fix first what people need to apply, enroll, pay, register, learn and get support: admissions and financial aid, registration, payment, housing, the LMS, required course materials, and emergency information.

5. Test. Combine automated scanning (it finds only part of the issues) with manual keyboard and screen reader testing and, ideally, testing by people with disabilities. W3C keeps a list of evaluation tools.

6. Remediate templates and platforms first. Fixing a site template or a theme fixes thousands of pages at once. Then fix high-traffic content, forms and documents.

7. Documents and media. Convert PDFs that people need to accessible HTML or properly tagged PDFs. Caption all recorded video, provide transcripts for audio, and plan captions for live events. Archive or remove what nobody needs.

8. Courses. Give faculty accessible templates, training and support for course materials; build checks into course design and LMS review.

9. Procurement. Require ACRs, test high-impact products, add contract language, and track vendor commitments.

10. Exceptions. Document every exception you rely on, with evidence that each condition is met, and review it when content changes.

11. Access on request. Publish an accessibility statement with a way to request accessible formats and report barriers, set response times, and log every request.

12. Train and monitor. Train everyone who creates or buys digital content, scan continuously, and report progress to leadership. Documented, continuous progress is your best evidence of good faith.

Checklists by role

Presidents and boards

• Name an accountable executive and fund the plan; accessibility is now a compliance deadline, not a project.
• Ask for a quarterly progress report against the inventory.
• Confirm who is designated to make undue burden determinations.

General counsel

• Confirm which rules and dates apply, including state law.
• Approve the policy, exception criteria, contract clause and determination process.
• Track NFB v. DOJ and any DOJ proposed rule.

CIO and IT

• Own the inventory, testing tools and template remediation.
• Make accessibility a release requirement for every system.
• Require accessibility review for new platforms and major upgrades.

Procurement

• Require a current ACR for every relevant purchase and renewal.
• Add the contract clause, remediation timelines and remedies.
• Escalate high-risk products for independent testing.

Faculty and instructional design

• Use accessible templates; add alt text, headings and captions as you build.
• Choose publisher and courseware tools that conform.
• Know how to request help from your accessibility office.

Communications and web teams

• Build accessibility into the CMS, design system and publishing workflow.
• Retire or archive outdated content properly.
• Check social media posts for captions and alt text.

Disability services

• Coordinate individual accommodations alongside the institution-wide plan.
• Feed recurring barriers back to the working group.

Useful resources

Official

• ADA.gov fact sheet on the Title II web rule, with the 2026 extension.
• First steps toward complying with the Title II web rule from DOJ.
• The 2024 final rule and the 2026 extension in the Federal Register.
• 28 CFR 35.204: duties, fundamental alteration and undue burden.
• ADA National Network: free regional technical assistance (800-949-4232).

Standards and testing

• WCAG 2.1 and the WCAG 2.1 quick reference.
• W3C list of web accessibility evaluation tools.
• Section508.gov: testing guidance and how to evaluate an ACR.
• ITI's VPAT template for vendor Accessibility Conformance Reports.

Higher education practice

• WebAIM: guides, training and the WAVE checker.
• AHEAD, the Association on Higher Education and Disability.

Our free templates

The toolkit and template pack are built around the rules described above.

Sources

• Fact sheet: Title II web and mobile app rule, ADA.gov (updated for the 2026 extension)
• Final rule, Federal Register, April 24, 2024
• Extension of compliance dates, Federal Register, April 20, 2026
• DOJ extends digital accessibility compliance dates, Reed Smith
• HHS extends Section 504 web and mobile app deadlines, Duane Morris
• NFB sues DOJ and HHS over deadline extensions, Deque; case record, Civil Rights Litigation Clearinghouse
• Title II action needed, Lainey Feingold
• Accessibility rule for public schools, community colleges and public universities, United Educators
• 28 CFR 35.204, eCFR
• Education Department dismissed most student civil rights complaints, The 19th
• Texas v. Kennedy, DREDF
• Guidance on web accessibility and the ADA, ADA.gov, March 18, 2022