508 compliant PDF: what a federal reviewer checks

What “508 compliant” means for a PDF

There is no separate PDF rule in Section 508. A PDF is electronic content, and the Revised 508 Standards give electronic content one test:

A PDF you download is a non-web document: the standards define one as a document that is not a web page, not embedded in one, and not used to render one. So the rule reads WCAG 2.0 with one swap, set out in E205.4.1: wherever WCAG says “web page” or “page”, read “document”. 2.4.2 Page Titled becomes a test that the document has a title, and 1.4.2 Audio Control applies to sound that plays “in a document”.

Notice what the rule does not say. It never mentions tags, Acrobat or a particular checker. Tags are simply how a PDF passes criteria such as 1.3.1 Info and Relationships and 1.3.2 Meaningful Sequence, which is why every federal checklist starts with them. A reviewer judges the file against WCAG 2.0; the tools are how they get there.

Which PDFs the rule covers

Every PDF an agency makes available to the public must conform: a fact sheet, a tax form, a map, the minutes of a public meeting. Section508.gov's own examples include a PDF of an IRS tax form, a PDF map of parking at a national park, and a federal contract or grant template. Internal files must conform too when they fall into one of nine kinds of official communication:

• Emergency notifications
• Decisions on administrative claims or proceedings
• Program or policy announcements
• Notices of benefits, eligibility, jobs or personnel actions
• Formal acknowledgements of receipt
• Survey questionnaires
• Templates and forms
• Educational and training materials
• Intranet content designed as a web page

Records kept by the National Archives under federal recordkeeping law are excused unless they are public. Everything else in the two groups above is in scope, whoever wrote it. That is where a business comes in: when you deliver a report, a form or training material to an agency, it becomes the agency's document, and the solicitation will say which 508 provisions it must meet. Section508.gov's electronic documents overview puts it in one line: any publicly available electronic document or agency official communication must be Section 508 conformant.

PDF/UA: helpful, not required

PDF/UA-1 is ISO 14289-1, the standard for an accessible PDF file itself. Its requirements are consistent with WCAG 2.0, and a later part, PDF/UA-2, exists. When the Access Board wrote the 2017 standards, it proposed letting agencies accept PDF/UA-1 in place of WCAG 2.0 for PDFs, then changed its mind in the final rule. The reason is the most useful paragraph a PDF author can read about Section 508:

PDF/UA-1 survived in one place: an authoring tool an agency buys, if it exports PDF, must be able to export PDF/UA-1. For your file, treat a clean PDF/UA check as strong evidence about tags and structure, and then check contrast yourself, because no PDF/UA pass covers it. Free PDF/UA checkers such as PAC handle the first part; our contrast check handles the second.

What a federal reviewer checks

Agencies do not each invent their own list. The federal accessibility community keeps an ICT Testing Baseline for Electronic Documents, released as version 1.0 on 30 September 2024 and written by the Accessible Electronic Documents Community of Practice. It names what any 508 test of a document must cover, leaves the tools to the tester, and expects a separate test process for each file format, PDF among them. Three of its 24 tests are marked not applicable to documents; the rest are what a reviewer works through.

Read it as a buyer would. Many rows are things a checker can flag but only a person can settle: whether alt text says the right thing, whether a heading describes its section, whether the reading order makes sense. That is why the next section's checklist mixes tool readings with yes-or-no judgements.

The federal PDF checklist, as a reviewer fills it in

GSA's Section508.gov page on PDFs hosts the checklist that federal document testers wrote for themselves. It opens with preconditions before any detail is checked. An untagged or scanned file fails outright, and a file made in Adobe LiveCycle cannot be tested with Acrobat Pro. A PDF Portfolio or a file with attachments is tested one part at a time. And a PDF that runs scripts has, in the checklist's words, effectively turned into a software application, so it goes to the DHS Trusted Tester process instead. Here it is as a sheet you can fill in:

A worked example: one fact sheet, four fails

The sheet above is filled in for a two-page fact sheet exported from Word, the kind of file a contractor might deliver to an agency. It passes the gates and most of the detail. These are its four fails, and the criterion behind each:

• The file is called FS_final_v3.pdf

  The federal checklist asks for a file name that identifies the document. Rename it for what it is.

• The title bar shows the file name, not the title

  The title is set, but Initial View is not told to show it. That is a 2.4.2 Page Titled fail, read as “document titled”.

• The bar chart has no alt text

  A figure that carries data needs alt text that gives the point of the chart, and the numbers in a table or the text. That is 1.1.1 Non-text Content.

• The footnote is pale grey on white

  Text at that size needs 4.5:1. Checkers leave contrast to a manual check, and a person measured it at well under that. That is 1.4.3 Contrast (Minimum).

How a reviewer tests: the checker first, a person second

The federal checklist is written around Acrobat Pro's Full Check. PAC, the free checker published by axes4, checks many PDF/UA and WCAG requirements automatically, and its makers say a visual check by a person is still needed. Neither tool can tell whether alt text is right or whether the reading order makes sense, which is why every checklist line still ends in a person's yes or no. Our PDF accessibility check walks those judgement calls one at a time.

Contrast is the classic gap. Section508.gov's guide to testing contrast in documents says built-in checkers cannot test images of text and that manual testing should always be done, with a tool such as a colour contrast analyser. Large text, at 18 point or 14 point bold, needs 3:1; everything else needs 4.5:1.

The DHS Trusted Tester process is written for web content, so a plain PDF is not tested with it; a scripted PDF is, because it is treated as software. If a buyer asks who tested your files, a Trusted Tester certificate on your team is a strong answer either way. The program is explained in what Section 508 is.

When the PDF ships as part of a product sold to an agency, the buyer may also ask for an Accessibility Conformance Report, which section508.gov describes as covering software, hardware, electronic content and support documentation alike. Our guide to what a VPAT is explains the template and the report.

Handing a PDF to a federal buyer

• Ask whether a PDF is wanted at all

  Federal policy puts HTML first. If a web page or a Word file will do, the review is shorter.

• Build it right in the source file

  Headings, lists, alt text, table headers and colour are set in Word or InDesign, then exported with tags.

• Run a checker, then the review sheet

  The checker for structure; the sheet above for the calls only a person can make.

• Say what it meets, and how you know

  Name the standard and the method, not a badge. A sample note follows.

Never write “508 certified”: no one certifies a file. If your files also pass a PDF/UA-1 check, say so as extra evidence, not as the standard. With dozens of files to fix, compare PDF remediation services, which hand back tagged and checked files, with PDF remediation software for doing it in house.

Quick reference

This is general information, not legal advice. For your own situation, ask a lawyer.