Section 508 document testing: the ICT Testing Baseline for Electronic Documents and what federal testers check

"508 compliant" is stamped on a great many PDFs with no shared definition of what was tested. Since September 2024 there has been one: the ICT Testing Baseline for Electronic Documents, published on the U.S. Access Board's ICT Testing Baseline portfolio site. This guide explains what it is, who wrote it, what its 24 tests cover, and why it is useful well beyond the federal agencies it was written for.

What Section 508 requires of documents

Section 508 of the Rehabilitation Act requires U.S. federal agencies to make their information and communication technology accessible. The Revised 508 Standards, in force since 2018, incorporate WCAG 2.0 Level A and AA success criteria as the accessibility standard for electronic content, which includes non-web documents. A "non-web document", in the Baseline's words drawn from the standards, is a document that is not a web page, not embedded in a web page, and not used in the rendering or functioning of web pages. Section508.gov also records that agencies must prioritise HTML and use PDFs only when necessary, and provides authoring guidance, training modules, and checklists for the document types agencies produce most.

The Baseline and who wrote it

The ICT Testing Baseline portfolio, maintained on the Access Board's site, sets a common minimum for accessibility test processes so that different agencies' results are comparable. The Baseline for Electronic Documents, version 1.0 released September 30, 2024, covers all non-web documents. It was authored by the Federal Accessible Electronic Documents Community of Practice, the AED COP, which subject matter experts from several agencies established in October 2012 to improve accessible content and create reusable testing and authoring artifacts, together with a Baseline for Documents Technical Advisory Committee. Section508.gov's PDF training modules describe their guidance as based on the AED COP's Section 508 Baseline Test Guide for PDFs and the Section 508 PDF Checklist.

The 24 tests

The shape of the list is the point. It is organised by WCAG outcome rather than by PDF object, which makes it applicable to Word, Excel, and PowerPoint files as well as PDF, and it separates what a document must achieve from how a particular tool achieves it. Cross-reference tables in the Baseline's appendix map each test to the success criteria it covers.

Baseline, test process, and checker

Three layers are easy to confuse. The Baseline defines what must be tested and the pass criteria. A test process, such as the AED COP's test guide for PDFs, says how to test it step by step in a given tool. A checker, such as Acrobat's or PAC, automates the parts of a test process that software can decide; the checker comparison shows how much that leaves. A document is "508 conformant" in any defensible sense only when every applicable Baseline test has been carried out, including the manual ones, and the results recorded.

Using the Baseline outside government

• As a procurement definition. Instead of "must be 508 compliant", require that documents pass the ICT Testing Baseline for Electronic Documents and that the vendor supply the test record. It is free, public, and specific.
• As a review checklist. The 21 applicable tests map closely to the manual items in the 15-point PDF checklist; teams already using that can align their evidence to the Baseline's numbering.
• As a training syllabus. Section508.gov's PDF training modules and checklists are free and were written for non-specialists in agencies.
• As a reminder about format. The federal policy to prioritise HTML applies equally well to any organisation: a document that lives as a web page needs none of this testing in PDF form.

Frequently asked questions

Sources

The statements above rest on the primary sources below. Where a source is a law or standard, the version and date named in the text are the ones checked on the review date. This guide is general information, not legal advice.

1. U.S. Access Board: ICT Testing Baseline for Electronic Documents . Version 1.0 release date, scope statement, and the list of 24 tests.
2. U.S. Access Board: Section 508 ICT Testing Baseline Portfolio
3. Section508.gov: Create Accessible PDFs . Federal policy to prioritise HTML and use PDFs only when necessary.
4. Section508.gov: Module 0, Introduction and Background (PDF training) . The AED COP's formation in October 2012.
5. Section508.gov: Module 2, Testing a PDF for Accessibility . Guidance based on the Section 508 Baseline Test Guide for PDFs and the Section 508 PDF Checklist.
6. Section508.gov: Electronic Documents Overview (testing)