Federal guide

Section 508 PDF remediation for federal teams

Section 508 of the Rehabilitation Act requires federal agencies to make electronic and information technology accessible, including the documents they publish. The Revised 508 Standards incorporate WCAG 2.0 Level AA. This guide covers what that means for PDFs, who it applies to, and how to test.

Updated 8 min readBy the Remediate team

What Section 508 requires for documents

The Revised Section 508 Standards are published at 36 CFR Part 1194. For web content and electronic documents, the standards incorporate WCAG 2.0 Level AA by reference. Agencies must ensure that content is perceivable, operable, understandable and robust for people with disabilities, including people who use screen readers, magnification, speech input or keyboard-only navigation.

The Access Board’s guidance is explicit that documents are covered. A PDF posted on an agency site should have a logical reading order, headings, alt text, table headers, form labels, document language and a title. Scanned documents need a text layer before any of that is possible.

Who Section 508 covers

  • Federal agencies. Every agency, department and independent establishment in the executive branch, plus the U.S. Postal Service.
  • Contractors. Section 508 flows into federal contracts and procurement. Vendors may be required to provide an Accessibility Conformance Report (often a VPAT) and accessible deliverables.
  • Recipients of federal funds. Some programs impose accessibility requirements through funding terms, even where Section 508 itself does not directly apply.

State and local governments are covered by ADA Title II rather than Section 508, although the practical document work is similar. See the ADA Title II guide for those deadlines.

WCAG 2.0 AA versus WCAG 2.1 AA

Section 508 references WCAG 2.0 AA. The ADA Title II rule references WCAG 2.1 AA. WCAG 2.1 is additive: it keeps the 2.0 criteria and adds requirements such as orientation, reflow, non-text contrast, text spacing and content on hover or focus.

In practice, testing to WCAG 2.1 AA satisfies Section 508’s WCAG 2.0 AA requirements and prepares a document for state, local and international obligations. If you must choose one target for a mixed audience, 2.1 AA is the safer baseline.

Procurement, VPATs and vendor evidence

Section 508 is as much a procurement rule as a publishing rule. When buying a remediation tool or service, ask for:

  • an Accessibility Conformance Report (VPAT) covering the product’s own interface;
  • a description of how the tool produces tagged PDFs and whether it writes PDF/UA structure;
  • the testing method and the assistive technology used;
  • a sample remediated document you can test yourself;
  • a data-handling and retention description for uploaded documents.

“WCAG compliant” is a claim, not evidence. A sample file and a screen-reader walkthrough are evidence.

How to test a PDF for Section 508

  1. Check the text layer. Select text on a scanned page. If nothing selects, run OCR first.
  2. Read the tag tree. Verify headings, lists, tables, figures and artifacts in a PDF accessibility checker or Acrobat’s Tags panel.
  3. Check reading order. Use the reading-order tool and then listen with a screen reader. Multi-column layouts and sidebars are the usual failures.
  4. Test tables. Headers must be associated with data cells; merged cells must not break the order.
  5. Test forms. Tab through every field, confirm labels and tooltips, and trigger validation errors.
  6. Test at 200% zoom and with text spacing overrides. Content should reflow or remain usable.
  7. Record the result. Keep the checker output, screen-reader notes, date and reviewer.

Where Remediate fits in a 508 program

Remediate gives agencies a structured, screen-reader-ready reading experience for documents already published, while the original PDF remains the record copy. That helps with the long tail of reports and archives that cannot all be re-authored at once. For documents that must themselves conform — forms, official notices, records with legal retention requirements — pair the layer with file-level remediation.

Read the remediation guide for the file-level process, or open the live demo to test the viewer with a keyboard and a screen reader.

Frequently asked questions

Does Section 508 apply to PDFs?

Yes. Section 508 covers electronic documents published by federal agencies. The Revised 508 Standards incorporate WCAG 2.0 Level AA, including document structure, reading order, alt text, tables and forms.

Does Section 508 apply to contractors?

Section 508 requirements flow into federal contracts and procurement. Contractors may need to provide an Accessibility Conformance Report and accessible deliverables, depending on the contract.

Is WCAG 2.0 AA enough, or do we need 2.1 AA?

Section 508 references WCAG 2.0 AA. WCAG 2.1 AA is additive and is the safer baseline for agencies that also work with state or local partners covered by ADA Title II.

What is a VPAT?

A VPAT (Voluntary Product Accessibility Template) is the common format for an Accessibility Conformance Report. It records how a product meets Section 508 and WCAG criteria. It is a disclosure, not a certification.

Can a transcript replace a remediated PDF?

A transcript can provide an accessible path to the same information, but it does not automatically make the PDF itself conform. Agencies should remediate documents that must conform and use an accessible alternative for the long tail.

This guide is general information, not legal advice. Confirm your obligations with counsel and your accessibility office.

Make the next document readable by everyone.

Start with one report. See the transcript, translation and screen-reader experience your readers would get.