Student Recruitment
HTML vs PDF for University Recruitment Content
HTML vs PDF for prospectuses, international guides and agent packs: accessibility law, mobile reading, updates, analytics and when a PDF still makes sense.
14 minutes

Most universities still publish their prospectus, international student guide and agent pack as a PDF. Meanwhile, the accessibility team down the corridor is telling everyone else to stop. The University of Dundee’s web guidance says that in almost all circumstances content should go out as HTML, not PDF. The University of Chicago’s accessibility office makes a web page the default and keeps documents for print layouts and archives. In the US federal government, Section508.gov states that federal policy requires agencies to prioritise HTML and use PDFs only when necessary.
Recruitment content tends to sit outside that advice. It’s made by marketing teams, agencies and international offices, often in a design tool, and exported as a PDF because that’s how it has always been done. This post applies the HTML vs PDF question to the documents recruitment teams actually publish: prospectuses, viewbooks, international and country guides, and agent materials. It covers accessibility law, mobile reading, updates, analytics, agent and market versions, and flipbooks as a middle ground. It also covers the cases where a PDF is the right choice, because there are some.
We make theRACK, a recruitment content management system that publishes this kind of content as web pages, so we have a view. We’ll flag where it comes in. Nothing here is legal advice.
HTML vs PDF: the short answer
For recruitment content that people read on screen, that changes during the cycle and that exists in more than one version, HTML is usually the better format. For content that has to be printed, signed or kept as a fixed record, a PDF still makes sense. Point by point:
Accessibility: HTML is easier to make and keep accessible, because structure lives in the page. A PDF can be accessible, but only if it’s tagged and checked every time it’s exported.
Mobile reading: HTML reflows to fit a phone screen. Most PDFs keep their print layout, so readers zoom and scroll sideways.
Updates: a web page is one copy at one link. A PDF is a file that gets downloaded, forwarded and kept, so old versions keep circulating.
Analytics: a web page can show which sections people read. With a PDF, you mostly see the click that opened it.
Versions: country, language and agent versions of a web page can share one source. PDF versions are separate files to update and check one by one.
Print and legal records: a PDF wins. It looks the same everywhere, prints predictably and works as a fixed record of what was said on a date.
What we mean by HTML, PDF and flipbook
In PDF vs HTML discussions the terms get used loosely, so it helps to be precise.
HTML: a web page. The text is real text, headings are marked as headings and the layout adjusts to the screen. A digital prospectus or online viewbook is HTML, even if it’s designed to look like a publication.
PDF: a file with a fixed page layout, designed for print. It can be opened in a browser, but it behaves like a document, not a web page.
Flipbook: usually a PDF displayed in a page-turning viewer on the web. It’s hosted at a link and looks like a magazine, but underneath it’s still made of fixed pages.
The flipbook is the one that causes confusion. It lives on the web, so it feels like a web page. For accessibility, mobile reading and updates, though, it behaves much more like the PDF it was made from.
Are PDFs accessible?
They can be. A PDF that has been properly tagged, with headings, reading order, alternative text and the document language set, can work with a screen reader. The standard for this is PDF/UA (ISO 14289). The W3C notes that content in a PDF built to PDF/UA can be reflowed and zoomed for readers with low vision.
The catch is that accessibility in a PDF has to be built into the source file and checked again at every export. It doesn’t happen by itself. The Government Digital Service made the same point when it explained why GOV.UK publishes in HTML rather than PDF: unless they’re made with care, PDFs are often bad for accessibility. For a recruitment PDF that goes through three or four editions a cycle, in several languages, that care has to be repeated every time.
We’ve written a separate guide on how to make a PDF accessible under ADA Title II, so we won’t repeat the tagging steps here. If you have a backlog of PDFs and need to decide which ones to fix and which to rebuild, our post on PDF remediation for universities covers that decision.
What the law asks for
The rules differ by country, but all of them cover documents as well as web pages. In brief:
US, ADA Title II: the Justice Department’s web rule requires state and local government entities to meet WCAG 2.1 Level AA. Its small entity guide lists community colleges and public universities among them. An interim final rule published on 20 April 2026 moved the compliance dates to 26 April 2027 for entities serving 50,000 people or more, and 26 April 2028 for smaller entities and special district governments. The standard itself didn’t change.
PDFs under Title II: the rule covers what it calls conventional electronic documents, including PDFs. The Justice Department’s first-steps guidance describes an exception for preexisting documents, but it doesn’t apply to new content posted after the compliance date or to documents people currently use to access a service. Content a vendor provides for you is still your responsibility.
UK: the Public Sector Bodies Accessibility Regulations 2018 require public sector websites and apps to meet WCAG 2.2 AA and to publish an accessibility statement. PDFs published before 23 September 2018 are exempt unless people need them to use a service. Government guidance says most higher and further education providers are in scope, because of their dependence on public funding.
EU: for public sector bodies, the main law is the Web Accessibility Directive (EU) 2016/2102, which covers their websites and apps. The European Accessibility Act, which has applied since 28 June 2025, mainly covers consumer products and services such as e-commerce and e-books. Whether it touches any of your services is a question for your legal team.
One useful detail: WCAG 2.2 states that content conforming to 2.2 also conforms to 2.1. A recruitment publication built to the UK standard covers the US one too.

Mobile reading: where PDFs struggle most
A prospective international student is likely to meet your prospectus on a phone. An agent sends a link on WhatsApp, a counsellor forwards an email, or someone scans a QR code at a fair. A PDF designed for A4 or US Letter, viewed on a phone, means pinching, zooming and dragging the page from side to side to read each column.
That’s an accessibility problem as well as a usability one. WCAG’s reflow success criterion (1.4.10) asks that content can be read at a width equivalent to 320 CSS pixels without scrolling in two directions. A web page built for phones does this by default. A fixed-layout PDF usually doesn’t, unless it was built to PDF/UA and the reader’s app supports reflow.
Usability research backs this up. Nielsen Norman Group’s review of PDFs for online reading found that PDFs designed for print are hard to read on screen, slow to load on desktop and mobile, and easy to get lost in. Their advice is not to use PDFs for digital content that could be a web page. GDS made the same observation: PDFs aren’t designed to have a flexible layout, so readers end up zooming and scrolling in every direction.
For recruitment, this matters because the first read is often the only read. If the fees page is a two-page print spread squeezed onto a phone, the reader has to work hard just to find the number they came for.
Updating content: one link or many files
Recruitment content changes all the time. Fees are confirmed late, a scholarship is added in January, an entry requirement changes for one country, a visa rule moves. Each change creates a question: where is every copy of this document?
With a PDF, the honest answer is “everywhere”. It’s on your website, in agents’ inboxes, in shared drives, on a fair laptop and in a counsellor’s downloads folder. You can replace the file on the website, but the copies already downloaded stay as they were. GDS found that PDFs are less likely to be actively maintained, which leads to broken links and outdated information.
A web page is one copy at one link. Fix the fee once and everyone who opens the link sees the new figure, including people who saved it months ago.
A worked example
Take a fairly typical international guide:
Languages: 4 (English, plus three translated versions).
Agent versions: 6 (one per lead agency, with their contact details).
Updates in a cycle: 3 (fees confirmed, scholarship added, intake dates changed).
If each language and agent combination is its own PDF, that’s 24 files. Three updates means 72 exports. If the PDFs are meant to be accessible, each export needs its tags, reading order and alternative text checked again. And after each round, older copies are still circulating.
As web pages, the same content is one shared source with language and agent variations on top. Each of the three updates is made once. The accessibility of the template doesn’t change when the fee does.
Analytics: downloads or reading
Ask a recruitment team what they know about how their PDF prospectus is used and the usual answer is “downloads”. That’s roughly what the tools give you. Google Analytics 4 can record a file_download event when someone clicks a link to a PDF. That tells you the file was requested. It tells you nothing about whether anyone opened it, which pages they read or where they stopped.
GDS put it plainly: they can’t get as much information from analytics about how people use PDFs. And once a PDF has been forwarded, every further read is invisible.
A web page can be measured like any other page. That means section views, scroll depth, time on page, clicks on the “apply” or “book a call” link, and the country and language of the reader. For international recruitment, that last point is the useful one. You can see whether the Vietnam guide is actually being read in Vietnam, and which sections people skip.
Agent and market versions
Agents are where PDF problems compound. A university working with dozens of agencies in several regions will often send each one a pack: a prospectus, a fees sheet, a scholarship summary and a country guide, sometimes rebranded with the agent’s details. When the fees change, someone has to send the new pack to everyone and hope the old one gets deleted.
The questions to ask of any format are simple:
Can you change a fee once and have every agent’s version show it?
Can you see which agents’ links are being opened, and in which markets?
Can a version for one country carry its own scholarships, visa route and currency without becoming a separate document to maintain?
Can an agent send it on WhatsApp and have it read properly on the prospect’s phone?
A folder of PDFs can’t do any of that. A web publication with shared content and per-agent links can. Our page on agent materials shows how that works in practice.
Flipbooks: a middle ground with limits
Flipbooks are popular because they solve some PDF problems without asking anyone to change how the content is made. You upload the PDF you already have and get a hosted link, a page-turn effect and some view counts. For a team with no web resource and a finished print file, that’s a real step up from an email attachment.
The limits come from the fact that it’s still a PDF underneath:
Mobile: the page is still a fixed print layout, shrunk to fit a phone. Zooming helps, but the reading experience is still the PDF’s.
Accessibility: depends on the tool and on the source PDF. One of the best-known flipbook tools says in its own help pages that its viewer interface meets WCAG 2.1 AA but the pages themselves aren’t fully compliant, and suggests attaching a separate accessible PDF for screen reader users. So you’re back to remediating the PDF.
Updates: changing a fee usually means editing the source file, exporting a new PDF and uploading it again. Even where a tool lets you keep the same link, every change is still a full re-export.
Versions: each language or agent version is usually its own flipbook, made from its own PDF.
Analytics: whatever the tool reports is tied to pages of a print layout, not to sections of content like fees or entry requirements.
If you’re comparing flipbook tools, our post on Issuu vs FlippingBook vs Flipsnack covers the main ones side by side, and our page on Issuu alternatives looks at other options. On cost, our breakdown of the real cost of a university prospectus puts print, PDF and digital side by side.

When a PDF is the right choice
None of this means PDFs should disappear. University guidance that favours HTML still keeps a place for documents. Dundee lists printable forms, long legal documents and formal signed documents. Chicago mentions fixed print layouts and records captured at a point in time. For recruitment teams, that translates to:
Print runs: a printed prospectus for fairs, school visits or counsellors still needs a print-ready PDF. That’s a production file, not the version you send online.
Legal and contractual documents: signed agent agreements, offer terms and conditions, and anything where the exact wording on a date matters.
Fixed records: last year’s prospectus kept for reference, or the version a student applied under. Under Title II, archived content can fall under an exception, but only if it was created before the compliance date, is kept for reference in a clearly separate archive and hasn’t been changed since.
Forms to be completed on paper: some offline processes still need them.
Documents someone else requires as a PDF: a partner, a government body or an accreditor.
Even in these cases, the advice from GDS and Nielsen Norman Group is the same: don’t make the PDF the only option. Publish the content as a web page first and offer the PDF alongside it for people who want to print or keep a copy.
How to decide, document by document
Most institutions don’t need a policy on PDF vs web page so much as a quick test. For each recruitment document, ask:
Will the content change during the cycle?
Will most people read it on a phone?
Does it exist in more than one version, by country, language, programme or agent?
Do you need to know what people actually read?
Does it have to be a fixed, unchangeable record?
Is its main use printed?
If the answers to the first four are mostly yes, it should be a web page. If the answer to either of the last two is yes, keep a PDF, ideally alongside a web version. Applied to typical recruitment content, that gives:
Prospectus or viewbook: web page, with a print PDF if you still print.
International and country guides: web page. These change most and have the most versions.
Agent packs: web page, with per-agent links.
Fees and scholarship information: web page. Keep dated PDFs as a record if your terms require it.
Event and fair materials: web page behind a QR code, with print for the stand.
Agent agreements and signed terms: PDF.
Moving from PDF to HTML: a practical sequence
If you decide to move, a realistic order of work looks like this:
List every recruitment PDF you publish or send, with its owner, versions and how often it changes.
Rank them by how often they change and how many people use them. International guides and agent packs usually come first.
Rebuild rather than convert. Running a PDF through a converter tends to carry over the print layout and its problems. Restructure the content for the screen, with short sections and real headings.
Keep shared content in one place, such as fees, entry requirements and scholarships, so versions draw on the same source.
Keep a print PDF only where you need one, and generate it from the same content.
Replace links to old PDFs on your website and in agent portals, and tell agents which link to use.
Update your accessibility statement and give people a way to request other formats.
Set up measurement before launch, so you have a baseline for the first cycle.
If you’re choosing a tool to do this, our roundup of digital publishing platforms for universities groups the options by type.
Where theRACK fits
This is where our view comes in. theRACK is a recruitment content management system for universities. Prospectuses, international student guides, viewbooks and agent versions are published as live web pages, and the eduKUDU team builds and updates them for you. Most institutions are live in two to three weeks, and content updates turn around within 24 hours. Change it once. Update it everywhere.
Publications are built on templates designed to WCAG 2.1 AA, with an accessibility menu for readers, and analytics show engagement by country, section and agent. Teams that already use GA4 or Looker Studio can connect them. Pricing is credit-based. See how it works for a digital prospectus.
It isn’t a replacement for every PDF you hold. Signed agreements and print production files stay as PDFs. It’s built for the recruitment content that keeps changing and gets read on a phone.
Common mistakes
Treating a flipbook as a web page. It’s a PDF in a viewer, with the PDF’s accessibility and update problems.
Converting a PDF to HTML automatically and calling it done. The layout and reading order usually need rebuilding.
Fixing the website and forgetting the PDFs linked from it, or the copies sitting with agents.
Keeping the PDF as the main version and the web page as an afterthought. Make the web page the source.
Measuring downloads and calling it engagement.
Leaving translated and agent versions until last. They’re the ones most likely to be out of date.
Frequently asked questions
Is HTML better than PDF for accessibility?
Usually, yes. A well-built web page carries its structure, reflows on small screens and can be updated without losing accessibility. A PDF can be accessible if it’s tagged and built to PDF/UA, but that work has to be repeated every time the file is exported. Universities’ own accessibility guidance generally makes HTML the default.
Are PDFs accessible to screen readers?
They can be, but not by default. An accessible PDF needs tags, a logical reading order, alternative text and the document language set, and it should be tested with a screen reader. Many recruitment PDFs are exported from design files without this, which is why accessibility teams prefer HTML.
Flipbook vs PDF: what’s the difference?
A flipbook is usually a PDF displayed in a page-turning viewer at a web link. It’s easier to share than an attachment and can show some analytics, but the pages keep their print layout. Accessibility, mobile reading and updates mostly depend on the PDF underneath.
Do PDFs on a university website have to meet WCAG?
In most cases, yes. Under the US Title II rule, PDFs posted by public colleges and universities must meet WCAG 2.1 AA from the compliance date, with narrow exceptions for older documents nobody uses to access a service. In the UK, PDFs published since 23 September 2018 fall under the public sector regulations, which point to WCAG 2.2 AA.
Should we still offer a downloadable PDF prospectus?
If people ask for one, or you print, yes. Offer it alongside the web version rather than instead of it, and generate it from the same content so the two don’t drift apart.
If your recruitment content lives in a stack of PDFs that need fixing every time a fee changes, you can see how other institutions have moved them to web pages in our case studies, or read how theRACK handles accessibility.
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.
View more articles
Learn actionable strategies, proven workflows, and tips from experts to help your product thrive.


