Back

Back

Student Recruitment

ADA Title II for Colleges: Accessible Recruitment Content

What ADA Title II means for college recruitment content, which documents it covers, the new deadlines and how to make viewbooks and PDFs accessible.

12 minutes

A student wearing headphones studying in a university library

Recruitment content is the most public thing a college publishes. It's also often the least accessible. Viewbooks exported straight from a design file to PDF, scanned brochures, infographics with the text baked into the image, videos without captions and flipbooks that turn every page into a picture. A prospective student using a screen reader can't get much out of any of them.

For public colleges in the US, that’s now a legal problem as well as a recruitment one. The Justice Department’s ADA Title II rule requires web content, including the PDFs and documents you post, to meet WCAG 2.1 AA. The deadlines were pushed back in April 2026, but the requirement didn’t change. And the wider web isn’t in good shape: the 2026 WebAIM Million report found detectable WCAG failures on 95.9 percent of the top million home pages.

This guide explains what Title II requires, which recruitment content it covers, what WCAG 2.1 AA means for a viewbook or prospectus in practice, how to fix PDFs you need to keep and how to plan the work. We make theRACK, a recruitment content management system whose publications are built on accessible templates, so we have a view on PDFs versus web publications. We’ll flag where that view comes in. Nothing here is legal advice: check the specifics with your counsel.

What ADA Title II requires of colleges and universities

In 2024 the Justice Department published a rule under Title II of the Americans with Disabilities Act setting a technical standard for the websites and mobile apps of state and local governments. Public colleges and universities are covered. The standard is WCAG 2.1 Level AA, the Web Content Accessibility Guidelines published by the W3C.

The compliance dates depend on the size of the public entity. After an interim rule in April 2026 extended them by a year:

  • Entities serving 50,000 people or more: April 26, 2027. Most state universities fall here, because they’re part of state government.

  • Smaller entities and special district governments: April 26, 2028. Some community college districts fall here.

The extension moved the dates, not the duty. Public colleges were already required to provide accessible communication under Title II, and people can still file complaints about inaccessible content today.

What counts as web content

More than web pages. The rule covers text, images, video and audio on your site and apps, and what the rule calls conventional electronic documents: PDFs, Word files, presentations and spreadsheets. If you post a PDF viewbook, the PDF has to meet the standard, not just the page it’s linked from.

It also covers content you provide through vendors. The Justice Department’s first-steps guidance says a public entity can’t hand its obligations to a contractor, so a viewbook hosted on a vendor’s platform, a virtual tour or an application portal run by a third party is still your responsibility. Put accessibility requirements into those contracts.

The exceptions are narrow

The rule has a few exceptions, and the Justice Department’s small entity compliance guide is clear that they’re narrow:

  • Archived web content: content created before the compliance date, kept only for reference, held in a clearly marked archive and not changed since. Moving a current document into an archive folder doesn’t qualify.

  • Preexisting documents: PDFs and other files posted before the compliance date, unless people still use them to apply for, access or take part in a program. An application checklist from 2024 that’s still in use isn’t exempt. A document updated after the date isn’t either.

  • Third-party content: content posted by people who aren’t working for you, such as comments on a public page. It doesn’t cover vendors acting for you.

  • Individualized, password-protected documents: such as a specific student’s records.

Even where an exception applies, you still have to provide an accessible version when someone asks for one.

What about private colleges?

The Title II rule covers public institutions. Private colleges aren’t covered by it, but most receive federal funding, which brings obligations under Section 504 of the Rehabilitation Act, and accessibility complaints and lawsuits aren’t limited to public institutions. In practice, the WCAG 2.1 AA standard in the Title II rule has become the reference point across the sector.

The UK and Europe

UK universities have their own rules. The Public Sector Bodies Accessibility Regulations require public sector websites and apps to meet WCAG 2.2 AA and to publish an accessibility statement saying what isn’t accessible and how to get an alternative. The government’s guidance says most higher and further education providers are in scope because they depend on public funding. The Equality Act 2010 applies too.

A student wearing headphones while reading on a laptop

Why recruitment content is usually the weakest point

Most guidance on ADA compliance in higher education focuses on the main website and on course materials. University websites tend to get accessibility attention first, because web teams know the rules. Recruitment content often sits outside that process, made by marketing, agencies and international offices, in formats that are hard to make accessible:

  • Untagged PDFs: exported from design software without structure, so screen readers read the text in the wrong order or not at all.

  • Text inside images: infographics, fee tables and covers where the words are part of the picture.

  • Page-image flipbooks: tools that convert each PDF page into an image look polished but can hide the text from assistive technology.

  • Brand colors: light grey or pastel text on white. Low contrast text was the most common failure in the WebAIM Million, on 83.9 percent of home pages.

  • Video: student stories and campus tours without captions or transcripts.

  • Versions: every country, language and agent version of a document is one more file to fix, and one more to fix again when it changes.

The last point is the one that catches teams out. Remediating a single PDF is manageable. Keeping thirty versions accessible through a cycle of fee and deadline changes is where it falls apart.

Which recruitment content is in scope

For a public college, assume these need to meet WCAG 2.1 AA unless an exception clearly applies:

  • Viewbooks, prospectuses and program or course guides on your site, whether they’re web pages or PDFs.

  • Cost, scholarship and financial aid documents.

  • Application checklists, forms and instructions, which are in active use and so never covered by the preexisting-document exception.

  • International and country guides, including translated versions.

  • Agent and partner materials you publish online.

  • Event pages, flyers and agendas you post.

  • Recruitment videos, virtual tours and student stories.

  • Anything a vendor hosts or runs for you.

What WCAG 2.1 AA means for a viewbook or prospectus

WCAG 2.1 has dozens of success criteria. For recruitment publications, these are the ones that matter most:

  • Real text: headings, body copy and figures should be text, not pictures of text.

  • Structure: headings in a logical order, real lists and a reading order that makes sense when read aloud.

  • Alternative text: meaningful images described in a sentence. Decorative ones marked as decorative.

  • Contrast: at least 4.5 to 1 for normal text and 3 to 1 for large text against the background.

  • Reflow: content readable at 320 pixels wide without scrolling sideways. In practice, it works on a phone.

  • Captions: for every recruitment video, plus transcripts where you can.

  • Keyboard access: every link, button and menu usable without a mouse.

  • Clear links: “Download the scholarship guide” rather than “click here”.

  • Forms: labeled fields and error messages that explain what went wrong.

  • Language: the document’s language set, so screen readers pronounce it correctly, including in translated versions.

Writing alt text for recruitment images

Recruitment content is image-heavy, and alt text is where most teams get stuck. The test is simple: what would someone miss if they couldn’t see the image? Describe that, in a sentence, and skip phrases like “image of”. Some examples:

  • Campus photo on a cover: “Students crossing the main quad in autumn, with the library behind them.” Not “campus”.

  • Student portrait next to a quote: often decorative, because the quote and name are already in the text. Mark it as decorative rather than describing the person’s outfit.

  • Chart of graduate outcomes: give the finding, not the shape, such as “Most of last year’s nursing graduates were employed within six months”, with your real figure. Put the full data in the text nearby.

  • Fee or deadline graphic: don’t. Put fees and deadlines in real text, so screen readers can read them and you can update them without redesigning an image.

  • Map or campus plan: describe the purpose (“Campus map showing the three halls of residence near the main entrance”) and offer a text version of the key routes.

  • Logo: your institution’s name, and nothing more.

Whoever writes the copy should write the alt text at the same time. Leaving it to the person who exports the file is how it ends up blank or saying “IMG_0423”.

How to make a PDF accessible

If you need to keep PDFs, for print-ready downloads or documents you’re required to provide, fix them at the source rather than at the end. The federal government’s Section508.gov guide to PDFs is a useful reference. The basic process:

  1. Build accessibility into the source file in InDesign, Word or similar: real heading styles, alt text on images, real tables and lists.

  2. Export as a tagged PDF, with the document title and language set.

  3. Open it in a PDF editor such as Acrobat Pro and check the tags and reading order. Automated export rarely gets these fully right.

  4. Run the accessibility checker, then test with a screen reader. Automated tools catch only part of the problems.

  5. Aim for PDF/UA, the ISO standard for accessible PDFs, alongside WCAG.

  6. Repeat for every version and every update.

That last step is the expensive one. A 60-page viewbook that changes three times a cycle, in four languages, needs remediation twelve times over. Our guide to the real cost of a university prospectus covers the other hidden costs of PDFs.

Printed documents and a pen on a desk

PDF or web publication: which is easier to keep compliant?

This is where our view comes in. A PDF is a fixed copy, so accessibility has to be rebuilt each time the content changes. A web-native publication built on accessible templates keeps its structure as the content changes, because the headings, contrast, alt text fields and reflow are part of the template rather than the file.

Web publications also reflow on a phone by design, which covers the reflow criterion that most PDFs fail. And there’s one copy at one link, so there are no outdated, inaccessible versions circulating by email.

That’s the approach theRACK takes. Every publication starts on a template built to WCAG 2.1 AA, with documentation available on request, and our team builds and updates the publications for you. More on our accessibility page. Whatever you use, the principle holds: the fewer static copies you maintain, the easier compliance gets.

Video, virtual tours and events

Recruitment leans on video more every year, and it’s covered by the same rule. Every pre-recorded video needs accurate captions, not just automatic ones left uncorrected. Add a transcript where you can. If important information is only visual, like a tour guide pointing at buildings, describe it in the narration or provide an audio-described version.

Virtual tours need to work with a keyboard and a screen reader, or come with an equivalent text route through the same information. Event registration pages and forms need labeled fields. Live events should offer captioning and a clear way to request accommodations before the day.

Your accessibility statement and alternative formats

UK public sector bodies must publish an accessibility statement, and it’s good practice everywhere. For recruitment content, a useful statement covers:

  • Which standard you aim to meet, and which content doesn’t yet meet it.

  • How to request an alternative format, such as an accessible PDF, plain text or large print.

  • Who to contact, and how quickly you’ll respond.

  • How to report a problem.

Then make sure requests actually reach someone in admissions or marketing who can act on them. A prospective student who asks for an accessible version of the scholarship guide in March and gets it in May has missed the deadline.

A plan to get recruitment content compliant

A realistic sequence for the next few months:

  1. Inventory everything: every recruitment page, PDF, video and vendor-hosted publication, with its owner, format and traffic.

  2. Triage. Anything used to apply, pay or register comes first. Remove or archive what’s out of date.

  3. Fix the templates and brand colors, so every new piece starts accessible.

  4. Remediate the high-traffic documents, or rebuild them as web publications if they change often.

  5. Check your vendors. Ask for an Accessibility Conformance Report (often called a VPAT) and add accessibility terms to contracts.

  6. Train the people who create content, including agencies and the international office.

  7. Publish a way to request accessible alternatives, and respond quickly when people do.

  8. Re-check every cycle. Accessibility isn’t a one-off project when the content keeps changing.

If you’re mapping this against the wider recruitment calendar, our enrollment marketing guide sets out when content gets updated through the year.

Questions to ask vendors about accessibility

  • Which version and level of WCAG do you meet, and can we see your Accessibility Conformance Report?

  • Who is responsible for the accessibility of the content we publish on your platform, you or us?

  • Do you convert our files into images of pages, or publish real text?

  • How are PDFs and downloads handled?

  • Has the product been tested with screen readers and keyboard-only navigation, and by whom?

  • How quickly do you fix accessibility issues we report?

  • Will you put your accessibility commitments in the contract?

Read the answers to the second question carefully. Many platforms make their own interface accessible but make the customer responsible for the content. That’s fair, but it means the work still sits with your team. Our guide to choosing student recruitment software covers the rest of the buying process.

A person working on a laptop at a desk

Common mistakes

  • Fixing the website and forgetting the PDFs linked from it.

  • Assuming a vendor’s accessibility claim covers your content.

  • Relying on automated checkers alone.

  • Treating the extended deadline as a reason to wait. Complaints don’t wait for compliance dates.

  • Remediating a document once, then losing the fixes in the next edition.

  • Leaving international and translated versions until last.

Frequently asked questions

Does ADA Title II apply to private colleges?

The Title II web rule applies to public institutions, as part of state and local government. Private colleges aren’t covered by that rule, but most receive federal funding and have accessibility obligations under Section 504 of the Rehabilitation Act. Check your institution’s position with counsel.

When is the ADA Title II deadline for colleges?

After the April 2026 extension, public entities serving 50,000 or more people, which includes most state universities, have until April 26, 2027. Smaller entities and special district governments have until April 26, 2028. The duty to provide accessible communication already applies.

Do PDFs have to be accessible under Title II?

Yes. PDFs, Word files, presentations and spreadsheets posted on your website or app are covered. There’s a narrow exception for documents posted before the compliance date, but it doesn’t apply to documents people still use to apply for or access a program, or to documents updated after the date.

What WCAG level do recruitment materials need to meet?

WCAG 2.1 Level AA under the US Title II rule. UK public sector bodies, including most universities, are expected to meet WCAG 2.2 AA under the Public Sector Bodies Accessibility Regulations.

Does content hosted by a vendor count?

Yes. Content you provide through a contract or license, such as a viewbook on a vendor’s platform or a third-party virtual tour, is still your responsibility under Title II. Choose accessible vendors and put accessibility terms in the contract.

Are accessibility overlays or widgets enough?

No. Widgets that add a toolbar to a page don’t fix untagged PDFs, missing alt text or poor structure in the content itself. They’re no substitute for accessible source content.

If your recruitment content lives in dozens of PDFs that need fixing every time something changes, you can see how other institutions have moved to web publications in our case studies, or read how theRACK handles accessibility.