Accessibility Works Best as a Production Practice

What the rule sets

In April 2024, the Department of Justice published a final rule under Title II of the Americans with Disabilities Act, setting a technical standard for the web content and mobile apps of state and local government entities, which includes public colleges and universities. The standard is WCAG 2.1 Level AA (U.S. Department of Justice, Fact Sheet, 2024).

In April 2026, the compliance dates were extended by a year. As it stands now, public entities serving a population of 50,000 or more have until April 26, 2027, and public entities serving fewer than 50,000, along with special district governments, have until April 26, 2028 (Accessible.org, 2026; Seyfarth, ADA Title III blog, 2026).

The extension moved the date. It did not move the standard, and the general non-discrimination obligation applies the whole time regardless. Private institutions fall under Title III rather than Title II, but they still carry Section 504 obligations where they take federal funds, are held to Section 508 for federally funded procurement, and are mostly adopting WCAG 2.1 AA as the working standard regardless. Academic medical centers have a separate, nearer deadline under the 2024 HHS Section 504 rule.

The rule includes narrow exceptions. Genuinely archived content, certain pre-existing documents not used to apply for or take part in a service, third-party content outside the institution’s contract. The working test is simpler than the exception list: if a document is how a student registers, learns, or completes a course, it is in scope. And that includes course content delivered through the learning management system to enrolled students.

Why a production practice beats catching up

Every institution carries a back catalogue that needs bringing up to standard, so some remediation belongs in any plan. As the whole plan, though, remediation runs into a structural limit. It scales with how much content exists, not with how hard anyone works. It puts the effort at the end, where it costs the most. And it does not compound. A remediation project finishes, and the backlog starts refilling right behind it.

Building the accessible step into production changes the shape of the problem entirely. Accessible templates. An authoring tool that checks as people write. A gate built into procurement. A captioning pipeline with real capacity. Content owners who have been trained. Each of these reduces the inflow for good. WebAIM’s annual survey of the top million home pages keeps turning up detectable failures on most of them (WebAIM Million). A useful reminder that it is the workflow, not any one person’s effort, that determines the result.

There is a return here beyond compliance, too. Accessible design regularly helps people it was never aimed at. Captions for a student in a noisy room, or reading in a second language; clean heading structure for anyone working through a long page; keyboard operability for people who never touch a mouse. Designing for the edge tends to raise the middle.

The seven points where accessibility gets built

What makes this a practice rather than seven disconnected efforts is treating it as one program.

Procurement. Every product that faculty, staff, or students touch gets evaluated before purchase, against a current Accessibility Conformance Report with the key claims checked rather than filed away. This is the highest-leverage step, because the contract is where an institution’s real influence over a supplier’s code sits. Reading a conformance report well is its own topic.

The website and web applications. The public site, the portal, the application system. What the Title II rule most directly addresses. Fix it at the template level, not page by page.

The LMS and course content. The largest volume of content on most campuses. Accessible course templates, a checker that runs at authoring time, and real faculty support turn an unbounded backlog into a flow someone can manage.

Third-party instructional tools. Publisher courseware, homework platforms, proctoring, library databases. Licensed by the institution, outside your own code, so the contract is once again the point of leverage.

Documents. PDFs, slide decks, spreadsheets. The single most common category, and usually a matter of tooling and training more than anything else.

Multimedia. Captioning, transcripts, and audio description, run as a pipeline with committed capacity and a stated turnaround. Setting one up is well-trodden ground at this point.

The seam between the physical and the digital. Classroom capture, assistive listening, digital signage, kiosks, lab software. The point where accessibility turns into an AV hardware specification. This is the seam the connected classroom work exists to close.

The rest of the compliance surface

Two other obligations run through the same contracts and workflows, and a technology decision that accounts for them keeps you from creating tomorrow’s problem while solving today’s.

FERPA and data privacy. Every instructional tool that sees a roster, a grade, or a piece of student work is processing an education record. The questions that belong in the evaluation: what student data does this product collect, where does it live, who qualifies as a school official with a legitimate educational interest, and what happens to the data on exit. With the contract saying so in writing. The GLBA Safeguards Rule now reaches institutions handling federal student-aid data, which widens the set of products this touches.

Academic integrity technology. Plagiarism detection and remote proctoring are compliance tools with their own set of considerations. A detection score is one input among several, and a sound policy states plainly what weight a score can carry and what independent evidence a charge needs. Building that policy is covered on its own.

Sequencing the work toward the deadline

Start now by setting the procurement gate. An accessibility requirement built into procurement is the least expensive step available, and it keeps the volume from growing while you work the existing backlog. Run a prioritized audit alongside it. Public-facing and high-traffic content first, then the LMS template and the highest-enrollment courses, then documents and media.

Over the following year and a half or so, fix at the template level and build the pipelines. Remediate the web presence through accessible templates and a shared component library rather than one page at a time. Bring the LMS course template up to standard. Stand up the captioning pipeline, the document workflow, and the authoring-time checks. Start faculty support with the highest-volume material first.

In the run-up to the deadline, work the backlog while the pipelines keep running. Prioritize by exposure and traffic. Because the pipelines already exist, the backlog shrinks instead of refilling behind you.

At the deadline itself, this is a standing function. A named owner, a monitoring cadence that samples real content, and accessibility built into every new content and procurement decision going forward. Institutions that start now reach 2027 and 2028 with that capability already in place. The deadline is the forcing function. The practice is what you keep afterward.

The part that carries it: bringing faculty in

Faculty are being asked to bring years of course material up to a standard most of them were never taught. What works is handing them the tools to do it as part of normal authoring. A checker that flags issues as they write, a captioning service with a fast turnaround, templates that start accessible, and support aimed at their highest-volume material. It also means giving them a clear explanation of why the standard exists and whom it serves. Given a walkable path and a reason that makes sense, most faculty come along. And the capability the institution builds along the way is one it keeps.