All insights
,

Your website passed the audit. Your document library didn’t

Two tall stacks of paper files and documents with handwritten year labels ranging from 1991 to 2015

Accessibility audits have a comfortable habit of stopping at the website. The templates get checked, the colour contrast gets fixed, the accessibility statement gets published, and everyone moves on. Meanwhile, sitting quietly in the media library are eight years of committee minutes, conference programmes, annual reports and guidance notes — almost all of them PDFs, almost none of them accessible.

This spring, the US Department of Justice gave public institutions an unexpected gift. The ADA Title II digital accessibility deadline, originally set for April 2026, was pushed back a year — to April 2027 for larger public entities, including most public universities, and 2028 for smaller ones. The DOJ’s stated reason was that institutions simply weren’t ready, particularly on staffing and technology. The obligations themselves haven’t changed. Only the date has.

If you run the web presence for an association, society or university, the question worth asking is not “have we been let off?” but “what do we do with the year we’ve just been handed?” Our suggestion: spend it on your documents, because that’s where the real gap is.

What the rules actually say about documents

The Title II rule doesn’t stop at web pages. It requires “conventional electronic documents” — PDFs, Word files, presentations and spreadsheets — to meet WCAG 2.1 AA, the same standard as the rest of the site. There are exceptions, and they’re narrower than people assume. Documents posted before your compliance date are exempt, but only if they’re not currently used to apply for, access or take part in your services. Properly labelled archive sections are exempt. Individualised, password-protected documents are exempt. And even where an exception applies, the underlying duty remains: if someone requests an accessible version, you still have to provide one.

UK readers never had the grace period in the first place. The Public Sector Bodies Accessibility Regulations have required accessible office documents since 2018 — anything published after 23 September that year must comply, and older files lose their exemption the moment they’re needed for what the regulations call active administrative processes. The European Accessibility Act, in force since June 2025, added its own document obligations for in-scope services across the EU.

Three regimes, one consistent message: the downloads section of your website is part of your website.

Why documents are always the weak point

Membership organisations produce documents the way other organisations produce emails. Board papers, standards, consultation responses, journal issues, event programmes, AGM notices — most of them written by a committee member in Word, exported to PDF, and uploaded by whoever had access to the CMS that afternoon.

Nothing in that workflow ever tags a heading, describes an image or sets a reading order. The result, for a screen reader user, is a wall of undifferentiated text — if the text is selectable at all. We’ve reviewed association sites where the website itself was in decent shape and the document library ran to thousands of files, of which a rounding error were accessible. Nobody planned that. It accumulated.

A triage that actually scales

The mistake is treating this as a remediation project: thousands of files, a per-document cost, a horrifying total, a report that gets filed. Treat it instead as a sorting exercise. Every document in your library belongs in one of four piles.

Delete or archive

A surprising share of any document library is simply dead: superseded policies, programmes for conferences that happened in 2017, duplicate uploads. Delete what serves no one. Move what’s kept for the record into a clearly labelled archive, which the US rule explicitly accommodates.

Convert to pages

Most PDFs on an association website are web pages wearing a trench coat. A two-page guidance note has no business being a download. Rebuilt as an ordinary page in the block editor, it inherits your theme’s accessibility for free, works on phones, and can actually be found by search — including the AI kind. This pile should be your biggest.

Remediate properly

Some documents genuinely need to stay documents — things people print, sign, or cite by page number. These get the full treatment: tagged headings, alt text, reading order, a meaningful title. It’s slow work, which is exactly why you do it only for the files that earn it.

Leave, but be ready

Genuinely exempt files can stay as they are — provided you have a working route for someone to request an accessible version and an honest accessibility statement that says so.

Fix the tap, not just the bucket

None of this holds if next month’s committee papers arrive as untagged exports. The lasting fix is upstream: accessible Word templates for the people who actually author these things, a house rule that content goes up as a page unless there’s a reason for a file, and a publishing step that checks documents before they reach the media library rather than years afterwards. That’s boring, unglamorous governance — which is usually what compliance looks like when it’s working.

If you’re not sure how big your own problem is, an afternoon with a crawl of your media library will tell you. In our experience the pile is smaller than feared more often than it’s bigger — but it’s never nothing, and it’s much cheaper to sort while the deadlines are still politely in the distance.

The Tecology Brief

Get insights like this in your inbox.

Occasional, considered notes on academic digital — never noisy, unsubscribe in one click.

By subscribing you agree to our Privacy Policy. We only ever send The Tecology Brief — unsubscribe in one click, any time.

More insights

Animated demo in a browser window: a search for a conference fee refund finds the expenses policy, matched by meaning
Native WordPress
WordPress 7.1 and the search box that finally understands people
WordPress 7.1 arrives on 19 August with embeddings support in core — the foundation for search that understands meaning, not just keywords. What that means for research archives, knowledge bases, and member content, and five things to do before you switch anything on.
5 min read
Read article
Overhead view of hands highlighting documents on a desk
Digital Strategy
How to run a website RFP a specialist can actually answer
Feature matrices select for confidence, not competence — every agency ticks every box. Five questions that actually discriminate, from the other side of the table.
3 min read
Read article
white and blue printer paper
AI in Academia
WordPress 7.0’s AI foundations: what a university web team should actually do with them
WordPress 7.0 shipped its AI foundations in May — an abilities registry, a core AI client, and connectors you control. The real opportunity isn’t the features: it’s that AI on your website just became governable.
3 min read
Read article

Start a conversation

Tell us about the work you’re doing.

The best projects start with understanding the work behind them. Book a 30-minute call — no pitch deck, no pressure, just a conversation about what you’re trying to do.

Or email info@tecology.co — we reply within one working day.

Privacy Settings
This website uses cookies to enhance your browsing experience on our website and our services. You may revoke or change your consent settings at any time.

Accept all Essential only