ADA Title II and Section 504: What the Deadlines Mean for Your Online Courses

For twenty years, digital accessibility in American public education ran on case law and good intentions. That changed with two rules that do something the previous framework never did: they name a technical standard and attach a date to it. The Department of Justice rule under ADA Title II and the Department of Health and Human Services rule under Section 504 of the Rehabilitation Act both require conformance with WCAG 2.1 Level AA across web content and mobile applications — and both apply to the online courses, learning platforms and course materials that public colleges, universities and school districts put in front of students. This guide sets out what each rule requires, who is covered by which, how they interact with Section 508, and what to fix first if you are behind. It is a practitioner’s summary, not legal advice; your general counsel remains the authority on how the rules apply to your institution.

Two rules, one technical standard

The most useful thing to understand first is that these are separate legal instruments with different triggers, and they converge on the same technical requirement.

• ADA Title II applies to state and local government entities — which includes public universities, community colleges and school districts. Its trigger is being a public entity. The DOJ final rule sets WCAG 2.1 AA as the standard for web content and mobile apps, with compliance dates staggered by the size of the entity’s population.
• Section 504 applies to recipients of federal financial assistance. That is a wider net: it catches private institutions too, because federal student aid counts. The HHS rule likewise adopts WCAG 2.1 AA for web content and mobile applications.

Because the technical standard is the same in both, the practical planning question is not “which rule applies to us?” but “which deadline comes first for us?” — and for most institutions, at least one of them already has. Confirm your own dates with counsel: they turn on entity type and, under Title II, on population size.

Note the version. Both rules name WCAG 2.1 AA, not 2.2. Building to 2.2 AA is nonetheless the sensible target, because 2.2 is backward-compatible — it adds nine criteria to 2.1 without removing any — so conformance with 2.2 satisfies a 2.1 requirement and insulates you from the next revision. There is no scenario in which targeting the older version saves work.

What counts as covered content

Institutions consistently underestimate the surface area. Under these rules, covered web content is not just the public website. In a teaching context it reaches:

• The learning platform itself — the LMS, its player, its assessment tools and its mobile app.
• Course materials — lecture video, slide decks, PDFs, spreadsheets, images and third-party publisher content delivered through your systems.
• Non-credit and outreach programmes — continuing education, pre-college, summer, executive and public-facing courses, which frequently run on separate platforms bought outside central IT.
• Administrative journeys students must complete — registration, enrolment, financial aid, advising and library systems.
• Third-party tools integrated into courses. Procuring an inaccessible tool does not transfer the obligation to the vendor; the public entity remains responsible for what it puts in front of students.

That last point is the one that reshapes procurement. It is why reading a vendor’s VPAT properly stopped being a paperwork exercise, and why accessibility riders now appear in institutional contracts.

The rules do contain limited exceptions — for certain archived content, for pre-existing conventional electronic documents, and for individualised password-protected documents — but they are narrower than they sound and are frequently misread as a general grace period for old material. Any archived content still in active instructional use is not archived in the sense the rule means.

How this relates to Section 508 and EN 301 549

Section 508 is the procurement-side rule: it governs what federal agencies buy and develop, and it incorporates WCAG Level AA directly. Many institutions have used it as a de facto purchasing standard for years, which is why vendors publish Section 508 columns in their conformance reports. The new Title II and 504 rules do not replace it; they add an operational obligation on top of the purchasing one. You now have to run accessible services, not merely buy accessible products.

For institutions with European campuses or partnerships, EN 301 549 is the harmonised European standard referenced by the European Accessibility Act, and it also builds on WCAG. The happy consequence of this convergence is that one conformance programme, anchored on WCAG 2.2 AA, satisfies the technical substance of all four frameworks. You are not managing four rulebooks; you are managing one standard with four audiences. Our Section 508 and ADA guide for online training covers the procurement side in more depth.

What to fix first when you are behind

Most institutions cannot remediate everything before their date arrives. Regulators and plaintiffs alike distinguish between an institution with a credible, documented, prioritised plan and one with nothing. Sequence the work by how many students each fix unblocks:

1. Captions on video. The single highest-volume barrier in online courses, and the one most likely to generate a complaint. Automatic captions get you most of the way; the requirement is accuracy, so budget for review of the automated output rather than treating the raw transcript as done. See our guide to automatic captions in e-learning.
2. The platform’s core journeys. Sign-in, enrol, open a lesson, take an assessment, submit. If any of these fails by keyboard or screen reader, nothing downstream matters. Test with the mouse unplugged; it takes twenty minutes.
3. Documents. Untagged PDFs and slide decks are the second-largest volume problem. Prioritise required readings in high-enrolment courses over the long tail.
4. Images and alt text in course content, then colour contrast in your own templates and brand colours.
5. Faculty capability. Remediation without training is a treadmill: you fix last year’s courses while this year’s are produced with the same defects. Training is the only intervention that changes the inflow. See designing a faculty accessibility training programme.

Document the plan, the priority order and the reasoning, and keep a record of what you fixed and when. In an enforcement conversation, a dated remediation plan that is being executed is a materially different position from an institution that cannot say what it knew.

Who owns this at your institution

The most common reason an institution misses a deadline is not technical. It is that no single person was accountable, so the work fell between four offices that each assumed one of the others had it. Digital accessibility in a university touches IT, the disability services office, the teaching and learning centre, procurement, the web team, general counsel and every academic unit — which is a recipe for diffusion unless somebody names an owner.

The structures that work share a shape. There is a single accountable owner with a budget and a reporting line high enough to compel — usually a digital accessibility officer reporting to a vice-provost or CIO, not a coordinator inside a service desk. There is a standing group with the offices above represented, meeting often enough to unblock rather than to report. And there is a published policy stating the institution’s standard, who it applies to, and what happens when a barrier is reported.

Three responsibilities in particular need explicit homes, because they are the ones that habitually go unclaimed:

• Procurement gating. Somebody has to be empowered to say no to a purchase, or to require an accessibility rider before signature. If accessibility review is advisory, it will be overridden by whoever is in a hurry.
• Course content. The largest volume of barriers is created by academic staff producing teaching material, and no central team can remediate that at scale. Ownership here means a training mandate with a sponsor, not a remediation queue.
• Complaint intake. A published route for a student to report a barrier, an acknowledgement window, and a triage process that treats accessibility defects as defects rather than feature requests. This is also your early-warning system.

Write down what you decide. In an enforcement conversation, being able to show a policy, an owner, a plan and a record of what was fixed and when is a substantially different position from an institution that has been busy but cannot evidence any of it.

What this changes about buying software

Three practical shifts follow, and they are already visible in institutional purchasing:

• A current ACR becomes a gate, not a nice-to-have. Expect to be asked for one dated within twelve months, naming the WCAG version and level, with gaps disclosed.
• Accessibility riders enter contracts. A conformance commitment, a remediation window for reported barriers, and a right to re-test at renewal. Several large institutions now attach a standard rider to every software contract.
• Authoring accessibility starts to matter more than platform accessibility. A conformant platform that lets faculty publish uncaptioned video with no alt text will not keep you conformant. The platforms that help institutions are the ones that make the accessible path the default — prompting for alt text, generating captions, flagging contrast and low-quality structure before publish.

Eduspera publishes its own Accessibility Conformance Report against WCAG 2.2 AA, EN 301 549 and Section 508, generated from a versioned file in the product repository so it is re-issued with every release rather than written once and left to age. Known limitations are listed openly, axe-core runs in the deployment pipeline, and our HECVAT answers are public so a security reviewer can qualify us before the questionnaire is sent. Institutions can start from the 12-week pilot kit.

Frequently asked questions

Does ADA Title II apply to private universities?

Title II applies to state and local government entities, so private institutions are generally outside it. They are usually reached instead by Section 504, because accepting federal financial assistance — including federal student aid — brings an institution within its scope, and by ADA Title III as places of public accommodation. Most private institutions therefore face an equivalent obligation by a different route.

Do the rules require WCAG 2.1 or 2.2?

Both rules name WCAG 2.1 Level AA. Building to WCAG 2.2 AA is still the better target: 2.2 adds nine success criteria to 2.1 without removing any, so it satisfies a 2.1 requirement and protects you when the referenced version is next updated.

Is archived course content exempt?

Only narrowly. The exceptions cover content that is genuinely archived — kept for reference, not maintained or updated, and not in active use. Material still assigned to students is in active use regardless of when it was created, so a course from 2019 that is still taught is covered.

Are we liable for a third-party tool used in a course?

Yes. A public entity remains responsible for the accessibility of services it delivers, including through third-party software integrated into its courses. Procurement does not transfer the obligation, which is why conformance reports and contractual accessibility commitments have become standard practice.

What if we cannot remediate everything by the deadline?

Prioritise by student impact, document the plan with dates and owners, execute it visibly, and provide accommodations for individual students in the meantime. An institution with a credible remediation plan in progress is in a substantially stronger position than one that has not started or cannot evidence what it knew.