Does WCAG Apply to PDFs?
PDFs made available as web content can fall within WCAG requirements. Assess WCAG and PDF/UA separately, along with the applicable jurisdiction and scope.
A PDF provided as web content can fall within WCAG requirements. The legal scope and referenced version depend on the institution, jurisdiction, content and applicable rule. A file extension alone does not determine compliance.
Evaluate applicable criteria
For documents, common evaluation areas include meaningful text alternatives, programmatically determinable structure, reading sequence, keyboard operation of interactive content, title, language and contrast. Read the complete criterion and relevant exceptions; not every criterion applies identically to every static PDF.
W3C publishes WCAG 2.2 and PDF techniques for applying relevant requirements. Use the version named by the governing rule or policy and document which criteria were tested.
PDF/UA is complementary
PDF/UA defines PDF-specific accessibility requirements. The Matterhorn Protocol describes failure conditions for PDF/UA-1, including human checks. PDF/UA and WCAG overlap, but PDF/UA conformance does not automatically establish every applicable WCAG requirement or every student journey.
Check linked documents as well as pages
A web-page check may not inspect the contents of its linked PDFs. Confirm actual scanner coverage and evaluate important files directly. Passing page checks does not certify every linked resource.
The DOJ Title II rule sets WCAG 2.1 Level AA requirements for covered state and local government web content and mobile apps, subject to the rule's scope and exceptions. The April 2026 IFR extends the dates to April 26, 2027 for public entities with a population of 50,000 or more and April 26, 2028 for smaller public entities and special district governments. Determine the institution's cohort using DOJ's population rules; enrollment and federal funding alone do not determine it. Existing accessibility obligations continue before those dates.
Australian DDA/DSE obligations do not themselves prescribe a WCAG version or the US dates. Section 508 concerns federal ICT rather than every federally funded university. Assess other jurisdictions and procurement standards separately.
Aelira Core is beta software. Supported workflows can apply eligible partial fixes and record outcomes, but some inputs need manual work or cannot produce a downloadable remediated file. Review the actual saved output, unresolved findings and content preservation before publication. Automated scores describe implemented checks rather than accessibility conformance. Inspect the public source and release documentation and evaluate a representative authorized sample before planning a rollout.
Aelira Team
•Accessibility EngineersThe Aelira team is building beta accessibility tools for higher education. Institutions can evaluate selected checks and partial fixes on their own files, with human review required before publication.
Related Articles
What Procurement Should Demand in an Accessibility AI Contract: A Due-Diligence Checklist
Eleven proposed due-diligence terms for AI-assisted accessibility procurement. Adapt acceptance, evidence, data-flow and exit commitments to institutional needs.
FERPA, Cloud Inference, and the Data-Sovereignty Question Procurement Should Be Asking
Map document and inference data flows, review FERPA conditions and contract terms, and verify what a self-hosted deployment actually sends outside the institution.
What Accessibility Scores Establish — and Why Review Records Matter
Use scanner scores within their measured scope, and retain review records tied to exact files. Neither a score nor an audit trail guarantees conformance or an investigation outcome.