Back

Back

Student Recruitment

PDF Remediation for Universities: Fix or Rebuild?

PDF remediation at scale repeats every cycle. How universities decide which PDFs to fix, archive or rebuild as web pages, plus PDF/UA and flipbooks.

14 minutes

Curved library balconies lined with shelves of books

Ask a university web team how many PDFs sit on the website and you’ll usually get a guess. Ask how many would pass an accessibility check and the guess gets quieter. Prospectuses, course guides, international student guides, agent packs, fee sheets, scholarship flyers, last year’s open day programme. Years of them, uploaded by different teams, most exported straight from a design file.

PDF remediation is the work of fixing those files so people who use screen readers and other assistive technology can use them. For one document it’s a manageable job. For a backlog of hundreds, with new versions arriving every recruitment cycle, it becomes a budget line and a staffing problem. It also raises a question worth asking before anyone starts tagging: should this file be a PDF at all?

This post is about that decision. It covers why remediation is on the agenda now, what PDF/UA and tagging involve, what remediation costs in effort at scale, how to sort a backlog into remove, archive, remediate or rebuild, and whether flipbooks get you off the hook. They don’t, and the vendors say so themselves. If you need the step-by-step for making a single PDF accessible, our ADA Title II guide covers it.

We make theRACK, a recruitment content management system that publishes prospectuses and guides as accessible web pages, so we have a view on PDFs versus web content. We’ll say where that view comes in. This isn’t legal advice: check your institution’s position with counsel or your accessibility lead.

Why PDF remediation is on every university’s list

Two sets of rules put recruitment PDFs in scope. A third source tells you what governments themselves think of the format.

US: ADA Title II

The Justice Department’s Title II web rule makes WCAG 2.1 Level AA the technical standard for the websites and mobile apps of state and local governments, and public colleges and universities are part of that. Documents count. The ADA.gov small entity compliance guide defines web content as including “text, images, sound, videos, and documents”, and PDFs are named in the rule’s exception for older documents.

The dates moved this year. An interim final rule published on 20 April 2026 pushed them back by a year. According to ADA.gov’s fact sheet, the compliance dates are now:

  • Public entities with a population of 50,000 or more: 26 April 2027.

  • Public entities under 50,000, and special district governments: 26 April 2028.

Most state universities are likely to fall in the first group, because they’re part of state government. That leaves larger public universities until spring 2027. Our Title II guide covers the rule in more detail, so here we’ll stick to the parts that affect triage.

The exceptions are narrow. A PDF posted before your compliance date is exempt only if it isn’t currently being used to apply for, access or take part in your programmes. Archived content qualifies only if it was created before the compliance date, is kept only for reference, research or recordkeeping, sits in a dedicated archive area and hasn’t been changed since it was archived. ADA.gov’s first-steps guidance puts it bluntly: “Just putting content into an archive isn’t enough.” The same page says you can’t contract your responsibilities away to a vendor.

UK: the Public Sector Bodies Accessibility Regulations 2018

UK universities work under the Public Sector Bodies Accessibility Regulations 2018. GOV.UK’s guidance says public sector websites and apps need to meet WCAG 2.2 AA and publish an accessibility statement.

The PDF exemption is narrower than many teams assume. Regulation 4(2)(a) exempts office file formats published before 23 September 2018, unless the content is needed for active administrative processes. GOV.UK puts it more plainly: older documents are exempt unless users need them to use a service. Anything published since then is in scope. And if you want to argue that fixing something would be a disproportionate burden, GOV.UK says you have to carry out an assessment, and you can’t count lack of time or knowledge.

What governments say about PDFs

The US federal accessibility site, Section508.gov, says PDFs “are often not the most accessible or mobile-friendly option”, and that federal policy requires agencies to prioritise HTML and use PDFs only when necessary. That policy is for federal agencies, not universities. It’s still a useful signal from the people who write the rules.

What PDF remediation involves

Remediation means adding or fixing the structure that assistive technology relies on. A PDF that looks fine on screen can be a jumble to a screen reader if that structure is missing. The work usually covers:

  • Tags: marking every heading, paragraph, list, table and image so the document has a structure tree.

  • Reading order: making sure a screen reader moves through columns, sidebars and pull quotes in the right sequence.

  • Alternative text: describing meaningful images, and marking decorative ones as artefacts so they’re skipped.

  • Tables: header cells set up properly, so fee and entry requirement tables make sense when read aloud.

  • Document settings: title, language, embedded fonts, and bookmarks for long documents.

  • Forms and links: labelled fields, and link text that makes sense out of context.

  • Colour contrast: often impossible to fix in the PDF itself, so it goes back to the design file.

We won’t repeat the how-to here. The ADA Title II guide has the steps. What matters for planning is the standards you’re working to and how much of the work a machine can do.

PDF/UA and WCAG: two standards, one file

PDF/UA is the common name for ISO 14289, the international standard for accessible PDF. The Library of Congress format description sums up PDF/UA-1 (ISO 14289-1:2014) as a constrained form of PDF 1.7 built for assistive technology: all real content tagged, a logical reading order, alternative text on figures, embedded fonts, and meaning that doesn’t depend on colour or layout alone. A second part, ISO 14289-2:2024, known as PDF/UA-2, covers PDF 2.0 files.

WCAG is the standard the law points to. Roughly speaking, PDF/UA is about how the file is built and WCAG is about whether a person can use what’s in it. For WCAG PDF work, the W3C publishes 23 PDF techniques showing ways to meet WCAG success criteria in a PDF, and says plainly that they aren’t required. A remediation report that covers both standards tells you more than one that covers either alone.

Some WCAG criteria are hard for a PDF however well it’s tagged. Success criterion 1.4.10, Reflow, is Level AA. It asks for content to work at a width equivalent to 320 CSS pixels without scrolling in two directions. A two-column A4 page was never designed for that.

Why automation only gets you part of the way

Auto-tagging tools and accessibility checkers are good at finding problems quickly. They can’t decide what an image means, whether a reading order makes sense or whether a line of bold text is really a heading. The Library of Congress notes that converting existing documents to PDF/UA “is not straightforward or easy to automate”. That’s why proper remediation includes manual review and screen reader testing, and why it costs what it does.

Hands typing on a laptop, with a desktop monitor behind

The real cost of PDF remediation at scale

Remediation services usually price per page, with higher bands for tables, forms and dense layouts. Prices vary, so get more than one quote. But the price per page isn’t what drives the total. The number of pages does, and how often you have to fix them again.

A worked example

Take a mid-sized university’s recruitment PDFs over one cycle. These numbers are made up for illustration, so swap in your own.

  • Undergraduate prospectus: 80 pages, updated twice. That’s 160 pages.

  • Postgraduate prospectus: 60 pages, updated twice. That’s 120 pages.

  • International student guide: 40 pages in four languages, updated three times for fees, visas and deadlines. That’s 480 pages.

  • Country guides: 12 guides of 12 pages, updated twice. That’s 288 pages.

  • Agent pack: 30 pages in six regional versions, updated three times. That’s 540 pages.

  • Course guides: 40 subject guides of 8 pages, updated once. That’s 320 pages.

That’s 1,908 pages to remediate in a single year, before anyone touches the backlog. Multiply by your per-page quote and you have the recurring bill. Then add the internal time: briefing the vendor, checking what comes back, re-uploading, fixing links, and tracking down the old version an agent downloaded in March.

Look at where the pages come from. The two prospectuses, the documents everyone thinks of first, are 280 of the 1,908 pages, about 15 per cent. The rest comes from versions and updates. A remediation plan that budgets for “the prospectus” will be out by a long way.

Costs that don’t show up on the quote

  • Rework: a fee changes on page 23 and the file goes back for remediation, or someone edits the tagged PDF and breaks the tags without noticing.

  • Version drift: the fixed file goes on the website while an untagged copy keeps circulating by email and on agents’ websites.

  • Testing: someone has to check returned files with a screen reader, or you’re taking the vendor’s report on trust.

  • Design fixes: contrast problems and text baked into images go back to the designer, not the remediator.

  • Accessible-format requests: each one is a small job with a deadline attached, and an applicant’s deadline won’t wait for yours.

How to triage a PDF backlog

Not every PDF deserves remediation. Some should go, some can be archived properly, some need fixing, and some should stop being PDFs. Start with an inventory of every PDF linked from your recruitment pages: owner, date posted, last update, page count, downloads, and whether anyone uses it to apply, pay or register.

Then sort each file into one of five piles.

  • Remove: anything superseded, duplicated or out of date. Last year’s fee sheet, the 2023 open day programme, three copies of the same brochure. Deleting is the cheapest remediation there is. Redirect any links that point to it.

  • Archive: genuinely historic material kept for the record, such as old prospectuses. Under Title II it has to meet all four archive conditions, so it lives in a clearly marked archive area and stays unchanged. In the UK, the pre-September 2018 exemption covers it unless people need it to use a service.

  • Remediate: documents that need to stay as documents and rarely change. Formal policies, signed agreements, a form that has to be printed and posted, a document a regulator or accrediting body wants in a fixed format.

  • Rebuild as a web page: recurring recruitment content that changes every cycle, comes in several versions or gets heavy traffic. Prospectuses, course guides, international and country guides, agent materials, viewbooks.

  • Replace with a link: PDFs that repeat what’s already on a course or fees page. Point to the page instead.

Five questions to ask of every file

  • Is it used to apply for, pay for or take part in something? If so, it’s in scope now and goes to the top of the list.

  • Will it change before next September? If so, remediating it today buys you a few months.

  • How many versions exist across languages, regions, agents, print and digital?

  • Does anyone genuinely need it as a fixed document, for print or a formal record?

  • Does anyone open it? Your analytics will show which files nobody has downloaded in a year.

A file that’s in active use, changes often and exists in several versions is the strongest case for a rebuild. A file that’s stable, rarely changes and needs a fixed format is a fair case for remediation. In our experience, most recruitment PDFs fall into the first group.

Colleagues discussing plans around a laptop at a meeting table

A timeline to April 2027

For a large US public university, a workable sequence from now looks like this. UK teams can use the same order. Their regulations already apply.

  • December: inventory every recruitment PDF, with owners and download figures. Agree the rules for each of the five piles.

  • January: delete and redirect the dead files. Move historic material into a proper archive. Brief content owners on what’s changing.

  • February: remediate the documents that must stay as PDFs, starting with anything used to apply or pay. Commission rebuilds of the recurring content.

  • March: publish the rebuilt prospectus, guides and agent materials as web pages. Replace the old PDF links across the website, email templates and agent portals.

  • April: test with a screen reader and a keyboard, update your accessibility statement, and publish a clear way to request accessible formats.

  • Every cycle after that: check new content before it goes live, not after.

Tools, services or a rebuild?

There are three ways to get the work done, and most institutions end up using more than one.

Doing it in-house with tools

Acrobat Pro and similar editors, plus a checker, let your own team tag and fix files. It’s the cheapest route per file if you already have skilled people, and the slowest if you don’t. Remediation is a skill. Someone who does it twice a year will be slower and less reliable than someone who does it every day. In-house work makes sense for a small set of stable documents, and for fixing problems at source in InDesign or Word so future exports start in better shape.

Outsourcing to a remediation service

Specialist services work at volume and return files with a conformance report. That clears a backlog quickly. It doesn’t change the economics of documents that keep changing, because every new version is a new job. Before you sign, ask:

  • Standards: do you test against WCAG 2.1 AA and PDF/UA, and does that include manual screen reader testing?

  • Reporting: what does the conformance report show, and who signs it off?

  • Pricing: how do you price tables, forms and complex layouts?

  • Turnaround: how fast can you turn round a single urgent page change?

  • Source files: do you return accessible source files or only the PDF, and will our next edit undo your work?

Rebuilding recurring content as web pages

This is where our view comes in. For recurring recruitment content, rebuilding as accessible web pages removes the per-version cost. Headings, alt text fields, contrast and reflow sit in the template, so they survive the next fee change. There’s one live link per publication, so there’s no untagged copy sitting in someone’s inbox. And the page reflows on a phone by design.

You can do this in your own website CMS if the web team has room for long-form recruitment publications with regional and language versions. That’s often the sticking point. It’s also the gap theRACK was built for. The eduKUDU team builds your prospectus, international guides, viewbooks and agent versions as live web publications on templates built to WCAG 2.1 AA, then updates them when your content changes. Every publication also carries an accessibility menu so readers can adjust things like text size and contrast. That sits on top of accessible content rather than standing in for it. Most institutions go live in two to three weeks, and pricing is credit-based rather than per page. There’s more on our accessibility page, and US readers can see how it works for a digital viewbook.

A rebuild isn’t right for everything. A signed policy should stay a PDF, and a print run still needs a print file. For a fuller look at the two formats side by side, read our post on HTML vs PDF for university content.

Are flipbooks accessible?

Usually not on their own. Most flipbooks display each PDF page as a fixed page inside a viewer, and the vendors’ own documentation tends to separate the accessibility of the viewer from the accessibility of the pages. Where a flipbook does support screen readers, it usually relies on you supplying an accessible PDF or adding page text yourself. Turning a PDF into a flipbook doesn’t remove the need for PDF remediation. It often adds a second thing to check.

Here’s what three vendors say about their own products, checked on 18 November 2026:

  • FlippingBook: its help centre says the viewer interface meets Section 508 and WCAG 2.1 AA, but “the pages themselves are not fully compliant”. Readers who need the pages can download an accessible PDF that you supply.

  • Paperturn: its accessibility statement claims WCAG 2.2 AA for its website and product. Its accessibility feature page advises pairing a flipbook with a tagged PDF or HTML alternative for formal WCAG conformance.

  • Flipsnack: its pricing page lists WCAG 2.2 Level AA on all four plans. Its accessibility page describes the player as aligning with WCAG 2.1 AA, and asks creators to add a title and description for each page they want to be accessible, with AI-generated summaries to review before publishing.

None of this makes those tools bad at what they do. It means an “accessible flipbook” is usually an accessible viewer around the same pages, plus an accessible version you still have to produce and keep up to date. If you’re weighing flipbook tools against other options, our FlippingBook alternatives page compares them.

Keeping content accessible when it changes every cycle

Remediation projects tend to be planned as one-offs. Recruitment content isn’t. Fees change, entry requirements change, a course closes, a scholarship opens, visa rules shift. Every change to a remediated PDF either goes back through remediation or quietly breaks it.

A few habits make maintenance manageable, whatever format you use:

  • Fix at source: keep accessible styles in your InDesign and Word templates, so each export starts closer to compliant.

  • One owner per document: someone who knows when it changes and sends it for checking.

  • One live copy: share a single link rather than attaching files to emails, so old versions stop circulating.

  • Check before publishing: make accessibility part of sign-off, the way proofreading is.

  • Review each cycle: re-run the inventory every autumn, and move anything that’s become a frequent-change document to the rebuild pile.

If most of your backlog turns out to be documents that change several times a year, that’s a strong sign the format is the problem.

Common mistakes

  • Remediating everything in date order instead of starting with what people use to apply, pay or register.

  • Paying to remediate files that should have been deleted.

  • Moving current documents into an “archive” folder and assuming they’re exempt.

  • Taking an automated checker’s pass as proof that a file is accessible.

  • Fixing the English version and forgetting the translations and agent versions.

  • Editing a remediated PDF and breaking its tags without anyone noticing.

  • Treating a flipbook’s accessible viewer as if it made the pages accessible.

  • Planning remediation as a one-off project when the content changes every cycle.

Frequently asked questions

What is PDF remediation?

PDF remediation is the process of fixing an existing PDF so people who use screen readers and other assistive technology can use it. It usually means adding tags, setting a logical reading order, writing alternative text, structuring tables, setting the document’s title and language, and testing the result against WCAG and PDF/UA.

What is PDF/UA, and is it the same as WCAG?

PDF/UA is ISO 14289, the international standard for accessible PDF files. PDF/UA-1 applies to PDF 1.7 and PDF/UA-2 to PDF 2.0. It sets technical rules for how an accessible PDF is built. WCAG covers whether people can actually use the content, and it’s the standard that US Title II and the UK regulations refer to. Most accessibility teams check against both.

Do old PDFs have to be remediated under ADA Title II?

Not always. PDFs posted before your compliance date are exempt unless they’re currently used to apply for, access or take part in your programmes. Archived content qualifies only if it was created before the compliance date, is kept for reference in a dedicated archive area and hasn’t been changed since it was archived. Check the specifics with counsel.

Do UK universities have to make old PDFs accessible?

Under the Public Sector Bodies Accessibility Regulations 2018, PDFs and other office documents published before 23 September 2018 are exempt unless they’re needed for active administrative processes, which in practice means people need them to use a service. Documents published since then are in scope, and GOV.UK expects public sector websites to meet WCAG 2.2 AA.

Is it cheaper to remediate a PDF or rebuild it as a web page?

For a stable document that rarely changes, remediation is usually cheaper. For recurring recruitment content, such as prospectuses, international guides and agent packs that change several times a cycle and exist in several versions, the cost of remediating every version every time adds up fast. Rebuilding as an accessible web page puts the accessibility in the template, so an update doesn’t restart the work.

If your PDF backlog is mostly prospectuses and guides that change every year, you can see how other universities have moved them to web publications in our case studies, or find out more about theRACK.

Working on your recruitment content?

Get a free audit of your prospectus, viewbook or brochures from our experienced team, with 25 years in higher education. Or book a demo to see how theRACK keeps content current across every market.