April 24, 2026 Is the Web and App Accessibility Deadline. Are You Ready?

As the April 24, 2026 deadline approaches, public universities are not choosing whether to “do accessibility.” You are choosing how to run accessibility every day across web, apps, content, and the third-party tools your teams rely on. In April 2024, the U.S. Department of Justice finalized a rule under ADA Title II that makes WCAG 2.1 AA the technical standard for state and local governments’ public web content and mobile apps. It is not a guidance memo. It is a schedule with dates. Public entities that serve 50,000 or more people must comply by April 24, 2026. Smaller public entities and special districts have until April 26, 2027. After that, you keep meeting the standard as part of normal operations.

This is not only a compliance story. It is governance, staffing, procurement, and change management. Treat the timelines like fiscal deadlines, and you will end up with a calmer, more predictable digital operation that serves more people well, every day.

If you are a private university, Title II does not apply. Adopting WCAG 2.1 AA as your operating standard still pays off. It improves the experience for students and families across devices, lowers support tickets, steadies releases, and aligns you with what vendors and partners expect as expectations mature.

What actually changed and who is on the hook

Public universities live inside larger public entities, which is why the timelines feel close. A flagship does not follow student headcount. It follows the state’s population. That matters for planning. Treat the deadline like a fiscal close. Staff and budget in the current cycle, not the next one. If you run a multi-campus system, set one operating standard and let campuses flex tactics to fit their mix of programs and audiences. The rule is about the experience people have, not the number of org charts involved.

Here is the core shift in plain language. WCAG 2.1 AA now defines what compliance looks like for public-sector web content and for mobile apps. State and local governments are covered, which includes public universities and contractors delivering services on their behalf. Deadlines are based on the population of the public entity you belong to, not student headcount. A state university follows the state’s population, which is why many institutions fall into the earlier April 24, 2026 window.

Two practical implications follow. Your mobile experiences are in scope alongside the website, including student apps, navigation, wellness, transit, and events. The clock is running toward an operating date, not a one-time launch, so the work must fold into everyday processes.

What this means on campus

Think in terms of how you run, not “finish a project.” The Title II rule covers public content such as program pages, admissions and aid, registrar, bursar, housing, athletics, libraries, museums, and campus safety. It reaches media workflows for videos, livestreams, and podcasts where captions and transcripts are part of the core work. It touches documents, especially living forms that people use to apply, request, register, and pay. It reaches third-party flows you make available, for example calendars, ticketing, maps, chat, payment, parking, shuttle trackers, and appointment scheduling. It also applies to any mobile app the university offers or arranges for students or the public to use. The scope reflects how universities actually deliver services today, as a network of sites, tools, and vendors.

Course experiences carry the same expectations students bring to public pages. That does not mean an audit of every historic lecture. It does mean a forward plan for the classes you are teaching now and the content you promote. Give faculty a simple path that does not add busywork. Let the LMS do what it is good at. Use accessible templates for headings and lists. Make caption requests a one-click choice that lands in a queue your media team can see. Confirm the timeline before the course starts. When people can see the path and the dates, they follow the process because it helps them teach.

You do not need to boil the ocean. You do need a leadership stance that makes accessibility a stable operating standard rather than a series of emergency remediations. That is the same mindset behind building systems that self-heal instead of relying on heroics. For more, see my story Smarter Integrations That Help Your System Heal Itself.

About those exceptions

The rule includes limited exceptions, for example truly archived web content, some pre-existing documents, pre-deadline social posts, and content posted by third parties you do not control. These are narrow and do not change your obligation to provide effective communication when an individual needs access. The rule allows “conforming alternate versions” only when a genuine technical or legal barrier prevents you from making the primary content accessible. It is not a path to a separate site that drifts out of date. If you budget around exceptions, you will fall behind next year. Build the everyday path instead.

Leadership moves that make this stick

Most of your risk lives in the long tail of tools that sit between a student and a task. Ticketing, maps, calendars, chat, payment, housing portals. Write a short rule you can use everywhere. New or renewed contracts include an accessibility report that points to working examples, and a remediation service level tied to the experiences you are making public. If a vendor needs time to close a gap, publish a date and show what you are doing in the interim. People do not expect perfection. They expect honest status and a path that moves.

Universities run on coordination. Accessibility will stick when it is owned like any other operating standard, such as safety, privacy, or finance controls. Name one accountable owner with executive cover and a clear charter. Form a small working group that includes marketing and web, IT, LMS leadership, procurement, disability services, and legal. Make procurement a real gate by baking WCAG 2.1 AA into RFPs, renewals, and statements of work. Ask vendors for evidence such as VPATs with working demos and require remediation service levels on critical paths like paying, applying, and registering.

Treat templates and components as products with versions. When you ship a new page template, announce what changed, how to use it, and when the old one will retire. Do the same for video players, forms, and navigation patterns. Small, steady refactors are less expensive than annual sweeps. Train for the jobs you actually have. Designers need practical rules for color and contrast that still look like your brand. Editors need clear habits for headings, link text, alt text, and documents. Engineers and testers need to verify focus order, keyboard behavior, and aria patterns inside components. Media teams need a caption cadence and an accuracy bar for flagship content. This is the same “operate with constraints” stance that keeps work moving during tight budgets. See my story Efficient Growth in Uncertain Times.

Where to invest first and why  

1. High-stakes funnels. Admissions and aid, program pages, application help, portal and payment access, and registrar deadlines. If a student cannot read it, navigate it, or submit it, nothing else matters.
2. Media that drives decisions. Caption and transcribe the videos people use to choose a program, attend an event, or complete a task. Automation can help, and human review should own accuracy on flagship content.
3. PDF triage. Convert living forms to HTML, archive true history, and remediate only the subset still used operationally. Do not let a PDF habit turn into a backlog you cannot maintain.
4. Third-party surfaces on critical paths. Ticketing, calendars, maps, campus safety, payment, and transit. Put vendors on the hook in contracts and run pre-flight checks before you promote a flow.

PDF is where good intentions become backlog. Forms that change every term should live on the web where they can be read on a phone, validated before submission, and translated by assistive tech without friction. Keep a small team that handles conversions at the start of each term. Give them a calendar and a contact list. The first quarter is the hardest. By the second, the habit saves time for everyone who touches the form.

Notice what is missing. There is no promise to fix everything by a date. You will make the most important experiences reliably accessible, then roll improvements outward on a schedule leadership understands.