Accessibility on Demand™
Accessibility on Demand™
Which PDF standards apply? (ADA Title II/III, Section 508, WCAG 2.1/2.2, PDF/UA)
ADA Title II/III
Public sector (Title II) and public accommodations (Title III) are expected to provide accessible digital content. Most agencies use WCAG AA as the practical target for PDFs and web content.
Section 508 (U.S. Federal ICT)
Federal agencies must ensure accessible electronic content; the 508 refresh aligns with WCAG. Many programs now target WCAG 2.1/2.2 AA for consistency.
PDF/UA (ISO 14289)
The PDF-specific standard for tagging, semantics, and reading order so assistive tech can interpret documents. AoD aligns outputs to PDF/UA alongside WCAG conformance.
Comparison: WCAG, PDF/UA, Section 508 (quick look)
What do auditors check in a PDF for WCAG/PDF/UA?
Tags & structure — Correct headings, lists, tables, figures; meaningful landmarks.
Logical reading order — Intended flow across columns/sections.
Alt text — Concise descriptions for images/charts/icons; decorative items marked properly.
Tables — Header cells, scope, and correct associations with data cells.
Forms — Labels, roles, tab order, required indicators, and validation messaging (typically Expert Review).
Metadata & navigation — Document language, title, and bookmarks for longer files.
How we document PDF compliance (PAC report & Audit Pack)
PAC report
Objective conformance checks and warnings.
Remediation log
Actions taken, version/date, and notes for complex items.
Batch summary
File list, page counts, service levels, and target conformance.
Evidence you can keep: Clear, consistent artifacts for audits, procurement, and internal QA.
Do state laws change PDF accessibility requirements?
Many states and local governments publish additional digital accessibility policies. AoD anchors to the federal baseline (WCAG + PDF/UA) and can provide a state-specific compliance addendum—a short cross-walk mapping your state policy to AoD outputs—on request.
Official PDF accessibility resources
WCAG standard — W3C Web Accessibility Initiative
Section508.gov — PDF accessibility guidance
PDF Association — PDF/UA overview
PAC — PDF Accessibility Checker
ADA.gov — Web accessibility guidance
WebAIM — PDF accessibility techniques
PDF accessibility compliance FAQ
Is WCAG 2.2 required for PDFs?
Most U.S. programs target WCAG 2.1 AA today, with 2.2 AA adopted where applicable. AoD aligns outputs to WCAG 2.1/2.2 AA plus PDF/UA, so your PDFs meet current expectations and are future-ready.
What’s the difference between WCAG and PDF/UA?
WCAG defines accessibility outcomes; PDF/UA defines how a PDF is tagged/structured to achieve them. AoD uses both: WCAG for conformance goals, PDF/UA for correct tagging and reading order.
How do we prove a PDF is accessible?
Request our Audit Pack: PAC report, checks summary, and remediation log. It provides objective evidence against WCAG/PDF/UA and supports audits and internal QA.
Does ADA Title II/III specifically say “WCAG”?
Agencies commonly use WCAG AA as the practical standard for accessible PDFs and web content. AoD aligns outputs to WCAG and PDF/UA to support ADA and Section 508 programs.
Will our CMS or portal break tags after upload?
Some platforms compress or flatten PDFs. We share recommended settings and spot-check live links so published files retain WCAG/PDF/UA structure.
Get a sample PAC report
Get a sample PAC report and see AoD on your PDFs
Send two representative PDFs. We’ll return a short remediated example and PAC summary, plus a quick, transparent pricing confirmation.
"*" indicates required fields
Compliance note: This page is informational only and not legal advice.
Other contact options:
888-388-2276
info@caso.com
