TechnicalSep 2026 · 8 min read

Your Drupal Media Library Is a Hidden Accessibility Liability

Drupal does a lot right on accessibility. But the Media library, where years of PDFs and images pile up, is where compliance quietly slips, because nothing audits what is already there.

Drupal core is genuinely good on accessibility. It requires alt text on image fields by default and ships accessible admin and front-end themes. The gap is not the framework. It is the accumulation: the Media library grows for years, and no part of core ever looks back at what is already in it.

1Where Core Stops

Understanding exactly what Drupal does and does not cover is the whole point. Core validation fires on the content form. Everything below happens outside it:

PDFs uploaded as File or Media entities are never scanned for tags, reading order, or a text layer

Alt text is required on image field widgets, but not on images added through migrations, feeds, the JSON:API, or code

Alt text quality is never checked, so "image," "photo1," and the filename all pass

Nothing audits the thousands of files already in the library from past years

2Why It Is a Liability, Not Just Debt

Under the DOJ ADA Title II web rule, an inaccessible document that a resident needs is a failure whether it was uploaded yesterday or in 2014. The Media library is where the oldest, least-audited content lives, which makes it the highest-density source of risk on many Drupal sites. A once-a-year manual review cannot keep up with a library that grows every week.

3The Fix: Audit, Enforce, Convert

Audit the backlog

Scan every File and Media entity for accessibility, ranked by how many pages reference each one. This is what core never does, and it is where you start.

PDF Accessibility Remediator

Enforce beyond the content form

Extend validation to migrations, feeds, and the API, and flag placeholder alt text that technically passes but tells a screen reader nothing.

Alt Text Manager

Convert the documents people read

Rebuild high-value PDFs as pages so they leave the file system entirely and enter Search API as content.

PDF to Drupal Page

4Use Drush for Multisite

If you run a multisite platform, a state or university with dozens of subsites, a Drush command can scan the Media library of every subsite on a schedule, so governance happens once at the platform level instead of site by site. That is the difference between auditing a Drupal estate and auditing one Drupal site forty times.

Final Takeaway

Keep Drupal. The framework is not the problem. Put an audit, enforcement, and conversion layer on top of the Media library so the content that quietly accumulated for years is finally accounted for, and so the next upload cannot slip through the gap core leaves open.

See what is hiding in your library

Scan your PDFs for free, then bring the Media library under control with the Drupal accessibility modules.

See the Drupal Modules

PDF to Drupal: Paragraphs and Layout Builder

Layout Builder vs. Paragraphs for a Converted PDF

PDF Remediation: The Complete 2027 Playbook

Back to all articles