Section 508 is the US federal law requiring that information and communication technology (ICT) used by the federal government be accessible to people with disabilities — including PDF documents. If you sell to, or work for, a US federal agency, Section 508 applies to your PDFs. Here's what you need to know.
What Section 508 requires
Under the 2018 "refresh" (which harmonized Section 508 with Section 255 and adopted WCAG 2.0 Level AA as the technical standard), federal ICT — software, websites, documents, including PDFs — must conform to WCAG 2.0 AA. Because WCAG 2.1 AA is a strict superset of 2.0 AA, building to 2.1 AA (and PDF/UA-1) keeps you compliant with Section 508 and aligned with the newer ADA Title II and EAA requirements. For PDF documents, the machine-checkable target is PDF/UA-1 (ISO 14289-1).
Who must comply
- Federal agencies — must procure and use accessible ICT
- Federal contractors and vendors — via the Federal Acquisition Regulation (FAR), ICT delivered under federal contracts must meet Section 508
- Technology providers selling to the federal market
If your PDFs are deliverables in a federal contract — reports, manuals, forms, training materials — they're in scope.
Section 508 vs ADA Title II vs EAA
They overlap but cover different sectors and jurisdictions:
- Section 508 — US federal ICT (and contractors). See how it fits with the global picture in our laws overview.
- ADA Title II — US state and local government web content, including PDFs, with 2027/2028 deadlines. See the ADA Title II guide.
- EU EAA — private-sector products and services in the EU, effective June 2025.
For a PDF, the underlying technical requirements are nearly identical across all three: a tagged, PDF/UA-1-valid document that meets WCAG 2.1 AA. Build once, comply many.
What a Section 508-compliant PDF looks like
The same fundamentals apply: a real tag tree, document title and language, alt text on figures, logical reading order, and labeled tables and forms. Our compliance checklist covers each requirement. The good news: a PDF that passes these checks is compliant across Section 508, ADA Title II, and the EAA simultaneously.
Evidence and documentation
Federal procurements increasingly ask for accessibility conformance documentation (ACR/VPAT). Keeping a veraPDF validation report for each remediated document is your evidence that the PDF was checked against the standard — it supports your VPAT claims and stands up in an audit.
Check your documents
Run a free PDF/UA check on your federal-facing PDFs. If they pass, you're Section 508-ready at the document layer; if not, automated remediation fixes the structural failures in about a minute per document.
Sources and references
VPAT, ACR, and the procurement documentation you actually need
Federal procurements now routinely require a Voluntary Product Accessibility Template (VPAT) — or its successor, the Accessibility Conformance Report (ACR) — as part of the solicitation package. Here is what that means for PDFs:
- What a VPAT covers for PDF documents. The VPAT asks the vendor to declare conformance status for each Section 508 requirement. For PDF documents, the relevant sections are typically Chapter 5 (Software) or Chapter 6 (Support Documentation), depending on how the PDF is delivered. Each requirement gets one of four statuses: Supports, Partially Supports, Does Not Support, or Not Applicable.
- What "Supports" requires. For a PDF, declaring "Supports" for the document-structure requirements means you have validated the document against WCAG 2.0 AA (and preferably 2.1 AA) and PDF/UA-1, and the validation report confirms passage. You should be prepared to produce the validation report if asked.
- What "Partially Supports" means. This is the honest middle ground. A document that passes all structural rules but has judgment items pending (alt-text quality not yet human-reviewed, for example) is "Partially Supports" with a remark explaining which items remain and your plan to address them.
- The audit trail. Keep a veraPDF validation report per document, dated and stored with the document. In a procurement challenge or contract audit, the question is not "is this document accessible?" — it is "show me the evidence that you verified it." The report is that evidence.
How federal contractors typically handle PDF compliance (the practical playbook)
Based on the procurement patterns we observe, here is how federal contractors structure their Section 508 PDF workflow:
- At contract award: Identify all PDF deliverables in the Statement of Work. Tag them as Section 508 applicable/non-applicable. A blank fillable form submitted for approval is applicable.
- At each deliverable: Generate the PDF, validate with veraPDF, remediate structural failures, save the validation report. Bundle the report with the deliverable — not as a separate file, but as part of the submission package.
- At contract closeout: Provide a conformance summary listing each PDF deliverable, validation date, and pass/fail/partial status. This supports the contractor's overall VPAT/ACR for the engagement.
- Ongoing: If the PDF template changes (new branding, updated form fields), re-validate. Structural changes can break previously compliant documents.
Section 508 and the EAA: building one document for both markets
If your organization serves both U.S. federal and European markets, the good news is that Section 508 and the European Accessibility Act converge on the same underlying technical requirements — a tagged PDF that meets WCAG 2.x AA and passes PDF/UA-1 validation. A document prepared for a Section 508 submission satisfies the document-layer requirements of the EAA. The differences are in conformance documentation (VPAT in the U.S., Declaration of Conformity in the EU) and specific administrative processes, not in the document remediation itself. See our worldwide laws overview for the full jurisdictional comparison.