Accessibility prioritization without chaos: A practical triage model for higher ed

Higher ed accessibility teams are drowning in backlogs while new inaccessible content piles up faster than they can fix what’s broken. Effective triage isn’t about whoever complains the loudest. It’s about scoring user impact, reach, risk, and effort to create fix-now, plan, and defer buckets that prevent burnout and political warfare. This model gives accessibility leaders a defensible framework that connects mission-critical journeys to remediation capacity.

In a recent conversation with Chronicle Intelligence, we unpacked what this looks like in practice. You can review the key takeaways or watch the full discussion.

Triage without strategy burns out teams and invites lawsuits. Here’s how to build a prioritization model that works:

• Score content by user impact, reach, risk, and remediation effort.
• Focus remediation on mission-critical journeys that serve students, faculty, and the public.
• Remove or replace low-value content before you remediate it.
• Stop creating new accessibility debt while fixing the backlog.

Let’s start with why your backlog exists and why you can’t fix everything at once.

Start with the backlog but don’t drown in it

Backlogs exist everywhere. That’s unavoidable when April 2026 forces institutions to remediate decades of inaccessible content. Terrill Thompson from the University of Washington (UW) plainly describes it as “a backlog of inaccessible content that needs to be fixed.” The issue isn’t having a backlog. It’s treating that backlog like something you can clear through brute force.

That means most teams are wrongly approaching this. They’re trying to fix everything, which guarantees they’ll fix nothing that matters. A 50,000-page website doesn’t get remediated page by page. Hundreds of thousands of PDFs don’t get fixed one document at a time. The math doesn’t work, the budget doesn’t exist, and your team will burn out before you’re halfway through.

You need a defensible model for deciding what gets fixed now, what gets planned for later, and what gets removed entirely. Without that model, prioritization becomes politics. The department with the most influence jumps ahead in the queue. Mission-critical student journeys sit broken while someone remediates a seventeen-year-old PDF that gets five views per year.

Here’s what shifts when you treat triage as strategy instead of surrender: You stop pretending you’ll fix everything and start proving you’re fixing what matters. Leadership gets a roadmap instead of excuses. Teams know what they’re working on next month instead of firefighting whatever crisis landed in their inbox. Users see progress on the journeys that serve them instead of random fixes scattered across your digital footprint.

The backlog is real. The deadline is real. Your capacity is real. Triage makes all three work together instead of against each other.

Prioritize by mission-critical journeys

Higher ed accessibility programs default to fixing whatever’s easiest to count, such as courses in the LMS, PDFs in a shared drive, videos on the main website. That’s not strategy. That’s picking low-hanging fruit while ignoring whether anyone needs it.

Laura Rothstein clearly states that the April 2026 deadline focuses everyone’s attention on course content, but accessibility requirements reach beyond Canvas or Blackboard. Virtual tours for prospective students. Online housing applications. Athletic ticket sales. Hospital appointment scheduling. Alumni donation portals. If the public touches it digitally, it’s covered.

The scope isn’t fixing the LMS and calling it done. It’s every digital touchpoint across your institution. Most of those touchpoints matter more to your mission than some random fourteen-year-old PDF.

What happens if it stays broken?

A prospective student who can’t submit an application doesn’t enroll. A patient who can’t book a clinic appointment goes elsewhere. A faculty member who can’t access HR systems has a legitimate employment complaint.

Contrast that with low-stakes content: An archived event page from three years ago. A supplemental reading where the professor can provide an alternative. A departmental newsletter that reaches 40 people. While still covered by the law, the consequence of leaving these items broken while you fix registration systems is manageable.

Map remediation to user journeys

Journey	User impact	Examples
Admissions and aid	Prospective students can't apply or check aid status	Application portals, FAFSA tools, scholarship pages
Registration and enrollment	Current students can't add courses or view schedules	Course catalogs, registration systems, degree audits
Student services	Students can't access housing or health resources	Housing applications, health center portals, career services
Employee access	Staff can't complete required HR tasks	Payroll systems, benefits enrollment, training modules
Public services	External users can't access critical services	Hospital scheduling, event registration, public records

Thompson describes UW organizing teams around problems that needed solving, not just volume of content that needed fixing. Stop measuring progress by how many PDFs you remediate this month. Start measuring by which journeys work end-to-end for users who need accessibility features.

Your mission isn’t accessibility compliance. Your mission is education, research, and service. Triage around that.

Content type reality: Documents can dominate the queue

PDFs are the bane of every accessibility program. Cyndi Wiley at Iowa State puts numbers to what everyone feels: “hundreds of thousands of PDFs that we have in use.” Not just the ones created internally. That’s before you count publisher materials, journal articles, and third-party documents.

One unit on Wiley’s campus spent multiple years and grant funding on full-time positions solely to remediate thousands of PDFs. The result? They barely made a dent. When remediation contracts cost $100,000 to $150,000 annually and you’re looking at hundreds of thousands of documents, the math doesn’t work. Even at $5 per page on the low end, an 80-page PDF costs $400 to fix. Multiply that across your backlog, and you’re bankrupt before you’re halfway through.

Thompson talks about UW’s Think Before You PDF campaign that questions whether a PDF is the right format before anyone tries to remediate it. Could this be a webpage instead? An accessible Word doc? The answer is often yes. However, nobody asks because PDF became the default years ago.

The PDF problem compounds itself

PDFs dominate remediation queues for three reasons.

• Volume: They pile up faster than any other content type because everyone creates them.
• Complexity: Proper remediation requires technical expertise most staff don’t have.
• Cost: Whether you pay for tools, services, or staff time, PDFs eat budget.

Most institutions respond by throwing money at remediation services. That’s treating a symptom while the disease gets worse. Every week, faculty upload new inaccessible syllabi. Departments publish new forms. Communications sends out new reports. You’re remediating seven-year-old PDFs while year-old PDFs pile up behind them.

Thompson’s sustainability strategy makes sense. Stop creating new inaccessible documents before you drown in the backlog. That means procurement controls that reject tools producing inaccessible output, template libraries with accessibility built in, and CMS guardrails that prevent publishing broken content.

The fastest way to clear your PDF backlog isn’t better remediation tools. It’s stopping the flood of new PDFs that shouldn’t exist.

Remove or replace before you remediate

Wiley mentions PDFs sitting untouched on websites for three years. Dead content is your fastest win, and most teams ignore it.

Before you spend $400 remediating an 80-page PDF, ask: Does anyone use this? A seven-year-old event flyer getting five annual views doesn’t need remediation. It needs deletion. An outdated policy superseded by newer guidance doesn’t need fixing. It needs archiving or removal.

Thompson describes archiving as part of UW’s strategy. If content meets the ADA rule’s definition of archived material, label it accordingly and move on. That’s not avoidance. That’s smart resource allocation.

Triage options beyond fix it

Most teams see one path: find broken content, remediate it, publish it. Three options work better.

• Remove: Delete outdated, unused, or duplicate content.
• Replace: Swap inaccessible PDFs with accessible webpages or current documents.
• Archive: Label historical content that doesn’t require remediation under ADA rules.

The order matters. Remove first, replace second, remediate third. Every piece of content you remove is one less thing competing for limited remediation capacity. Every PDF you replace with an accessible webpage solves the problem permanently instead of paying for fixes every time the content updates.

Wiley’s point about unused PDFs applies across content types. That supplemental reading faculty posted eleven years ago? That backup version of a form replaced two years ago? Those image-heavy documents nobody opens? They’re clogging your queue while mission-critical content waits.

Stop remediating everything. Start eliminating what doesn’t deserve the effort.

A defensible triage model

Christina Adams from Siteimprove cuts to what matters: Prioritize what’s best for your users and what’s core to your business. Most programs lack a framework for making those calls, so decisions default to politics instead of impact.

Score content on four factors.

1. User impact: Does this enable a mission-critical task or simply provide supplemental information?
2. Reach: How many people encounter this content monthly? Ten or ten thousand?
3. Risk: What type of barrier does this create? What’s the likelihood someone gets blocked versus inconvenienced?
4. Effort: A quick fix requiring an hour or a heavy lift requiring specialized skills and vendor coordination?

Those scores create three buckets.

1. Fix now: High impact, high reach, manageable effort. Student registration systems, employment portals, admissions applications.
2. Plan: High impact but heavy lift. Complex enterprise systems requiring vendor remediation and testing cycles.
3. Defer, remove, or replace: Low-value content creating ongoing debt. Archived materials, outdated documents, duplicative resources.

The model works because it’s defensible. When a dean demands their content jump the queue, you have clear criteria showing why the registrar’s broken course catalog matters more than a departmental newsletter.

Triage without a model is favoritism with extra steps.

Triage fails if you continue to create new debt

Accessibility leaders often forget a critical point. You can’t make progress if new inaccessible content floods in faster than you can fix old problems. Remediation without prevention is expensive theater.

Adams describes slowing down the creation of inaccessible content as non-negotiable. That means controlling who can publish and what tools they can use. If everyone can post videos without captions, if faculty upload PDFs without accessibility checks, if departments buy tools that fail WCAG standards, your backlog grows faster than your team can work.

Prevention happens at two choke points

Procurement keeps inaccessible vendors out before contracts get signed. At Iowa State, Wiley’s team requires VPATs for every software review, but they verify them. Sales representatives filling out accessibility checklists isn’t the same as compliance. If the product fails, they negotiate remediation timelines into contracts or choose different vendors. Money is the only thing that forces vendors to fix their tools.

Content creation is harder because everyone publishes. Thompson talks about campaigns questioning whether PDF is the right format. Template libraries with accessibility built in. CMS guardrails that catch issues before publishing.

Adams pushes the governance angle further. Consider policies that limit who can create content or require workflows that catch problems before they go live. That feels restrictive until you realize the alternative is an endless backlog.

Triage clears the backlog. Prevention keeps it from refilling. You need both or you’re just treading water until the deadline passes and complaints start rolling in.

Make triage defensible, not political

Accessibility programs fail when prioritization becomes whoever complains the loudest. The triage model that works scores content on user impact, reach, risk, and effort then creates fix-now, plan, and defer buckets that leadership can defend.

That means shifting from “we’re fixing everything” to “we’re fixing what matters most.” Mission-critical journeys over random PDFs. High-traffic student portals over archived event pages. Content that blocks users over content that inconveniences them.

The framework only works if you can see what’s broken, who owns it, and whether you’re making progress. Platforms, such as Siteimprove, give accessibility leaders that visibility by crawling your entire digital footprint, scoring issues by severity, and mapping accountability to owners so you’re not hunting down who needs to fix what.

Triage without visibility is guesswork. Visibility without triage is paralysis. Combine both and you’ve got a program that scales past the April deadline and proves it’s working.

Request a demo to see how Siteimprove helps accessibility teams move from reactive fixes to strategic programs.