Plumb Works

If you work in IT, communications, or compliance at a public university, you’ve heard about the Title II accessibility deadline more than once — probably in a meeting where someone asked whether your institution is on track and no one had a confident answer. The question got asked, a date got repeated back, and the meeting moved on.

The question worth working on isn’t “what is Title II?” There are plenty of explainers for that already. The question is what the deadline requires your team to be doing right now, ten months out, and what being on track looks like once you get specific about it.

On track is narrower than most institutions assume, and the scope of the work is wider than most institutional leadership may realize.

You’re on the hook for more than the homepage

The rule covers web content and mobile apps a public entity “provides or makes available, directly or through contractual, licensing, or other arrangements.” Inside a university, that reaches the learning management system, the registrar’s portal, the housing application, every department subsite, every PDF syllabus, and each third-party tool a faculty member integrates into a course.

A typical university has hundreds of subsites, thousands of active PDFs, and countless third-party integrations that no central IT team fully inventories. Bringing all of that into conformance isn’t done in a sprint, and it isn’t primarily a code problem — it depends on procurement policy, content governance, and author training as much as it depends on engineering work. If that inventory hasn’t been built yet, ten months is tight, which is why it needs to start now.

The deadline confirms the standard. It doesn’t create the obligation.

The obligation didn’t start with this rule, and it won’t wait for the deadline either. Section 504 has required accessible programs and services since 1973, and both the Office for Civil Rights and private plaintiffs have been acting on that obligation for years. The DOJ rule clarified the technical standard and put a date on it, but it didn’t create the underlying requirement. A student who can’t complete a financial aid application because the form doesn’t work with a screen reader isn’t going to wait until April 2027 to file a complaint.

That distinction matters for how leadership reads the timeline. April 2027 is a regulatory deadline, not an enforcement start date — the risk doesn’t appear that day. It builds incrementally, every time a student is excluded from a process, and the date just makes a complaint much more likely.

Being on track means three things

First, inventory ruthlessly. Every domain, application, and embedded tool needs cataloged with an owner and a current accessibility state. Without this, remediation effort gets spent on low-traffic content while high-traffic blockers persist.

Second, prioritize by impact, not by ease. The pages a prospective student uses to apply, the portal a current student uses to register, the system a faculty member uses to submit grades — these come first regardless of whether they’re harder to fix than the marketing site. It’s tempting to clear the easy backlog first because the numbers look better in a status report, but that’s optimizing for the report instead of the user.

Third, treat third-party tools as a governance problem rather than a remediation problem. When a vendor’s product has a WCAG failure, the fix is to require the vendor to address it and make procurement contingent on conformance, not to build workarounds your team will have to maintain.

The DOJ already extended this deadline once, from 2026 to 2027, and stated it “fully anticipates implementing the regulation at the new deadline.” Treat that as the only extension you’ll get. It only affects the DOJ’s own enforcement timeline anyway — Section 504, OCR investigations, and private litigation were never on hold.

What to do this quarter

Build the inventory. Identify the five to ten systems with the highest combined traffic and harm potential. Get a real accessibility assessment on those systems — automated scans paired with manual testing using a keyboard and a screen reader, because automated tools miss most of what matters. Use the results to scope the remediation work and the procurement changes you’ll need to defend later.

One thing to watch for as that timeline pressure builds: overlay widgets that promise instant compliance through a line of embedded code. They don’t fix underlying markup, they don’t satisfy WCAG 2.1 AA, and they’ve drawn complaints and litigation of their own. If a vendor pitches a quick fix for the whole site, that’s a sign to slow down, not speed up.

The deadline is real, but the obligation is older than the deadline. April 2027 isn’t when accessibility becomes important; it’s when the regulatory case for not doing it runs out.

Plumb Works helps higher education and public sector institutions assess, prioritize, and remediate web accessibility issues. If you’re working through a Title II readiness plan and want a second set of eyes, get in touch.