If you sell to the U.S. government, accessible PDFs aren't a nice-to-have — they're a contract requirement. Federal agencies are bound by Section 508 of the Rehabilitation Act, and they pass that obligation straight through to the vendors they buy from. That means the reports, manuals, forms, and deliverables you hand over have to be accessible, and you'll often have to prove it before you win the work.
This guide explains how Section 508 shows up in solicitations and contracts, why it matters at bid time and at delivery, and a practical checklist for staying ready.
Why contractors are on the hook for Section 508
Section 508 directly obligates federal agencies to procure, develop, maintain, and use accessible information and communication technology (ICT). Agencies can't meet that duty if the things they buy aren't accessible — so the requirement flows downhill to contractors.
The technical standard is the Revised Section 508 Standards (the "508 Refresh," effective January 2018), which incorporate WCAG 2.0 Level A and AA by reference. For documents, that translates into the familiar accessibility fundamentals: tagged content, logical reading order, alt text on images, properly marked-up tables, accessible form fields, and correct metadata and language. Our Section 508 PDF compliance guide — the pillar for this topic — walks through what conformance looks like in detail.
The practical reality: when an agency buys your product or service, they're documenting that the purchase meets 508. Your deliverables are part of that record.
How 508 shows up in solicitations and contracts
Accessibility requirements appear at several points in the federal acquisition lifecycle:
- In the solicitation (RFP/RFQ). Through the Federal Acquisition Regulation (FAR), solicitations for ICT routinely include Section 508 provisions and ask offerors to describe how their products and deliverables conform. Increasingly, agencies ask for an Accessibility Conformance Report (ACR) up front.
- In the contract terms. Once awarded, 508 conformance becomes a contractual obligation, not a suggestion. Statements of work commonly specify that deliverables must meet the Revised 508 Standards.
- At deliverable acceptance. This is where many contractors get caught. An agency's contracting officer or 508 coordinator can reject deliverables that fail accessibility review. A non-conformant PDF report can hold up acceptance, payment, and the next milestone.
In short, accessibility is evaluated at the start (your bid), defined in the middle (the contract), and checked at the end (acceptance).
ACRs as part of your bid
The single most useful artifact for a federal contractor is a credible Accessibility Conformance Report — a completed VPAT. Agencies use it to evaluate whether your offering meets 508 before they award.
A strong ACR does two things: it demonstrates you understand the standard, and it gives the agency documentation to support their own compliance file. A weak or absent ACR signals risk. If you're not sure how to build one — including the four editions and how to use the conformance terms honestly — start with our guide to VPATs and ACRs for PDF documents.
A few bid-time tips:
- Use the Section 508 edition (or the combined INT edition) of the VPAT for federal work.
- Be honest. Accurate "Partially Supports" entries with specific remarks read as more credible than a sheet of "Supports."
- Tie the ACR to a specific product version and date it.
What "accessible deliverables" actually means
Agencies expect the documents you deliver to be usable by people relying on assistive technology. For PDFs, that means each file should have:
| Requirement | What it means in practice |
|---|---|
| Tags & structure | Headings, lists, and paragraphs marked up so a screen reader can navigate |
| Reading order | Content read back in a logical sequence, not jumbled |
| Alt text | Meaningful descriptions on informative images; decorative images marked as artifacts |
| Tables | Header cells associated with data cells |
| Forms | Labeled, navigable fields with clear instructions |
| Metadata & language | Document title and language set correctly |
These map directly to the WCAG criteria the Revised 508 Standards incorporate. A scanned image of a document with no text layer is the classic failure — it looks fine on screen and is completely opaque to assistive technology.
Consequences of non-conformance
Failing 508 isn't usually a dramatic courtroom event for contractors — it's a slow, expensive friction:
- Lost bids. Agencies can score or eliminate offers on accessibility. No ACR, or a poor one, can cost you the award outright.
- Rejected deliverables. Non-conformant documents can be bounced at acceptance, delaying payment and milestones.
- Rework at your expense. Fixing documents after delivery, on a deadline, costs far more than building them right. See the cost of PDF remediation for why retrofitting is the expensive path.
- Reputational and relationship damage. Agencies remember which vendors created accessibility headaches, and that follows you into future procurements.
- Complaints and oversight. Inaccessible federal content can trigger complaints and agency review, with the contractor's work in the spotlight.
A practical readiness checklist
Use this to get ahead of 508 before it costs you a contract:
- Know your obligations early. Read the solicitation's Section 508 / FAR provisions before you bid, not after award.
- Have an ACR ready. Maintain a current, version-tied ACR for your products and document templates so you're not scrambling at bid time.
- Build accessibility into your authoring workflow. It's cheaper to produce tagged, structured documents from the source than to remediate finished PDFs.
- Test before you deliver. Run both automated checks and manual / assistive-technology review on every PDF deliverable.
- Fix the source, not just the output. If your templates or export tools produce inaccessible files, repair them once instead of patching every document.
- Document your process. Keep records of how you test and remediate — useful at acceptance and for the agency's own compliance file.
- Re-test on standard changes. When standards or product versions change, refresh your ACR and re-validate.
The bottom line
Winning federal work means treating accessibility as a deliverable requirement from the first read of the solicitation, not a cleanup task at the end. Contractors who build accessible PDFs by default — and can prove it with a credible ACR — clear acceptance faster, protect their margins, and keep agencies coming back.
This is general information, not legal advice.
Key takeaways
- Federal agencies are bound by Section 508, and they push that requirement to contractors through FAR provisions, contract terms, and deliverable acceptance.
- The standard is the Revised 508 Standards, which incorporate WCAG 2.0 A and AA — meaning your PDFs need real tags, reading order, alt text, accessible tables, and forms.
- A credible ACR (completed VPAT) is increasingly expected as part of your bid; honesty and version-dating make it more, not less, persuasive.
- Non-conformance shows up as lost bids, rejected deliverables, costly rework, and damaged agency relationships.
- Build accessibility into your authoring workflow and test before delivery — fixing the source beats remediating finished files.
