We Ran veraPDF on 774 .gov & .edu PDFs (3.89M Failed Checks): Why 'Tagged' PDFs Fail ISO 14289-1 & Auto-Fix
When engineering teams audit websites for DOJ 28 CFR Part 35 (ADA Title II) or the European Accessibility Act (EN 301 549) , running axe-core against HTML templates is straightforward. Auditing—and repairing—legacy PDF repositories is a completely different binary puzzle. To quantify what actually breaks inside real-world public documents, we ran veraPDF ( ISO 14289-1:2014 / PDF/UA-1 profile)…
A comprehensive analysis of 774 PDF files from government and education domains revealed that 99.61% of them failed to meet the ISO 14289-1 accessibility standards. The majority of these failures (76.87%) were due to the presence of structure tags, even though the documents were technically tagged PDFs. This underscores the complexity of ensuring PDF accessibility, as the mere presence of tags is not sufficient.
The study identified several common issues that cause PDFs to fail validation, such as missing metadata, improper use of vector paths, missing language tags, and problems with embedded fonts. While these automated tools can repair many of these issues, they do not guarantee that the PDF will be fully accessible to users. The research emphasizes the need for human reviewers to verify the results, as automated tools cannot detect nuanced issues like correct reading order or meaningful alt text.
The full 2026 benchmark report provides detailed insights and open-source tools to help organizations address these challenges.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.