A WCAG 2.1 AA starting checklist for government PDFs
The U.S. Department of Justice (DOJ) Title II web rule requires state and local government web content and mobile apps to meet Web Content Accessibility Guidelines (WCAG) 2.1 Level A and Level AA success criteria. Portable document format (PDF) files, word-processor files, presentations and spreadsheets on a government site are "conventional electronic documents" under that rule. (28 CFR 35.104)
WCAG 2.1 is a World Wide Web Consortium (W3C) standard. The rule incorporates WCAG 2.1, W3C Recommendation of June 5, 2018. (28 CFR 35.104; 2018 Recommendation)
This page is not the full WCAG 2.1 standard. It is a starting list of success criteria that often show up in government PDFs. Checking these items — or passing an automated tool — does not mean a file "conforms" to WCAG 2.1 or is "Americans with Disabilities Act (ADA) compliant."
Not legal advice.
When this checklist is even relevant
The technical standard in 28 CFR 35.200 applies beginning April 26, 2027 for entities (other than special districts) with a total population of 50,000 or more, and April 26, 2028 for entities under 50,000 and for every special district government. Those dates were extended by one year in April 2026.
28 CFR 35.201 lists exceptions, including archived web content; pre-existing conventional electronic documents that are not currently used to apply for, gain access to, or participate in services, programs, or activities; and documents that are both about a specific individual, their property, or their account and password-protected or otherwise secured. Use this checklist first on new postings and on in-use forms, then decide with counsel about anything else.
DOJ publishes a small-entity compliance guide and a first-steps resource. DOJ's first-steps page also notes that some listings of the 2018 WCAG 2.1 text show an "outdated" banner; for purposes of the rule, DOJ says to use that 2018 version anyway.
Starting checks that often apply to PDFs
Each item below is a WCAG 2.1 success criterion from the June 5, 2018 Recommendation. Level A criteria are part of what the rule requires, not optional extras, because the rule requires both Level A and Level AA.
| # | Success criterion | Level | What to look for in a government PDF | What our automated checks cover | Still needs a person |
|---|---|---|---|---|---|
| 1 | 1.1.1 Non-text Content | A | Maps, seals, charts and informative photos have a text alternative that serves the same purpose. | Alt text is present on every image; decorative images are marked as artifacts (veraPDF) | Whether the alt text is accurate and useful |
| 2 | 1.3.1 Info and Relationships | A | Headings, lists and table headers are tagged as headings, lists and headers, not just styled to look like them. | Headings, lists, table headers and form labels are tagged (veraPDF plus our structure check) | Whether the structure matches the meaning (right heading level, right table header) |
| 3 | 1.3.2 Meaningful Sequence | A | The tagged reading order matches the meaning of the page, including multi-column agendas. | Our screen-reader simulation flags pages where tag order differs from the visual order | Whether the reading order makes sense when heard |
| 4 | 1.4.3 Contrast (Minimum) | AA | Live text and images of text have a contrast ratio of at least 4.5:1, with the exceptions listed in the criterion. | Automated contrast check: text color against the rendered background | Confirming flags by eye, especially text on photos and gradients |
| 5 | 1.4.5 Images of Text | AA | Prefer real text over a photograph of a page (a common issue with scanned minutes and fee tables). | Image-only pages are detected | Whether real text was supplied and is correct |
| 6 | 2.4.2 Page Titled | A | The PDF's document title describes the topic or purpose. | A document title is present and set to display (veraPDF) | Whether the title describes the document |
| 7 | 2.4.6 Headings and Labels | AA | Headings and labels describe the topic or purpose (for example, "Public comment," not "Heading 2"). | Headings and labels exist | Whether they describe the content |
| 8 | 3.1.1 Language of Page | A | The document language is set so a screen reader can pronounce the text correctly. | The document language is set (veraPDF) | — |
| 9 | 3.3.2 Labels or Instructions | A | Fillable fields have labels or instructions. | Each fillable field has a name (veraPDF) | Whether labels and instructions are clear |
| 10 | 4.1.2 Name, Role, Value | A | Each form field has a programmatic name, role and value that assistive technology can read. | Each form field has a name and role (veraPDF plus our structure check) | Whether the form works with a screen reader |
These are the checks our reports list. The “What our automated checks cover” column is what our tools check today. The “Still needs a person” column is what only a person can judge, and no person has done that review on our sample files yet. This table is a starting list. WCAG 2.1 Level A and AA include many other success criteria (for example, keyboard access, captions, and resize). A government website as a whole has to be considered, not only its PDFs.
Automated PDF checks are useful — and not enough
veraPDF is an open-source PDF checker. We use its PDF Universal Accessibility (PDF/UA-1) profile, plus structure checks, as part of a machine validation report. PDF/UA is a PDF-specific specification. It is not a substitute for WCAG 2.1, and a veraPDF pass is not a WCAG 2.1 conformance claim.
In our desk test of 6 public PDFs from small-city websites (42 pages) — minutes, newsletters, a scanned fee table and a fillable building-permit form — we recorded 2,690 failed automated checks before repair and 0 failed checks on all 6 files after, on November 18, 2026. The scanned fee table was rebuilt as 22 data tables with headers; the permit form's 43 fields each got a programmatic name.
Automated results only. No person with a screen reader has tested these files yet. A human screen-reader check is not available yet.
What Agendalight delivers with a repaired file
- The repaired file (we fix the document itself; we do not sell an overlay).
- A veraPDF PDF/UA-1 report and a structure check.
- A color-contrast report and a text-fidelity check.
- A screen-reader simulation transcript, labeled as a simulation, not a human test.
- A plain-English summary of what was tested, on what date, with which tools, and what still needs a person to check.
- An accessible HyperText Markup Language (HTML) version where it helps.
We do not claim the result is "ADA compliant" or that it "conforms" to WCAG 2.1.
Frequently asked questions
Is this the official WCAG 2.1 AA checklist? No. The official success criteria are in the W3C Recommendation. This page lists ten document-relevant criteria as a starting point.
If veraPDF reports zero failed checks, are we done? No. Automated checks miss meaning (is this alternative text accurate? does this reading order make sense out loud?). Our desk test is labeled as automated only.
Do all historical PDFs on our site have to meet this list? Not necessarily. See 28 CFR 35.201 and our guide to the archived-documents exception. Not legal advice.
Will you certify WCAG conformance? No. We report which listed automated checks each file passed and on what date.
Get in touch
Contact is coming soon. See the contact page for updates.
No checkout, no obligation.
Not legal advice. We report automated test results; we do not certify ADA or WCAG compliance. Learn more: WCAG 2.1 (2018) and the DOJ small-entity guide.