DEV Community

Loc Nguyen
Loc Nguyen

Posted on Edited on

ADA Title II (28 CFR Part 35) & ISO 14289-1 (PDF/UA-1): A Technical Remediation Guide for US Municipal & Higher-Ed Web Agencies

For digital agencies building Drupal, WordPress, or CivicPlus portals for U.S. cities, counties, community colleges, and special districts, the U.S. Department of Justice's 28 CFR Part 35 (ADA Title II) rule creates a concrete engineering challenge:

  • Phase 1 (April 24, 2026): State and local governments and public universities serving populations of 50,000 or more entered enforcement under WCAG 2.1 Level AA.
  • Phase 2 (April 26, 2027): Smaller municipalities (under 50,000 population), local school districts, community colleges, and special districts (water, transit, fire, libraries, parks) face the same WCAG 2.1 Level AA mandate.

Agencies usually ship clean semantic HTML, ARIA landmarks, and keyboard focus management in the CMS layer—only to discover hundreds of static PDFs sitting in /DocumentCenter/View/, board packet archives, fee schedules, and fillable permit forms.


Why Automated HTML Accessibility Overlays Miss Legacy PDFs

JavaScript accessibility widgets and HTML overlays run exclusively inside the browser DOM on HTML pages. They cannot modify or patch binary PDF object streams:

  1. Binary Document Tree Isolation: When a resident or screen-reader user opens a PDF in Chrome PDFium, Adobe Acrobat, or macOS Preview, assistive technology (NVDA, JAWS, VoiceOver) queries the PDF's internal /StructTreeRoot, /ParentTree, and content stream marked-content sequences (BMC/BDC ... EMC)—none of which any website JavaScript overlay can reach.
  2. Scoped Content Reality: Under 28 CFR Part 35, public-facing PDFs actively used for municipal services, permitting, budgeting, agendas, and admissions fall within digital accessibility obligations alongside HTML pages (subject to narrow regulatory exceptions).
  3. False Comfort Risk: Passing a web DOM scanner (Lighthouse or axe-core) on a municipality's homepage leaves PDF permit applications and Annual Comprehensive Financial Reports (ACFRs) completely untested.

The 5 Most Common veraPDF / PAC 2026 Failures on .gov and .edu PDFs

Running veraPDF 1.30.3 --flavour ua1 (the open-source reference validator for ISO 14289-1:2014) across public municipal and higher-ed PDF archives consistently surfaces five recurring failure clusters:

1. Clause 7.1 — Missing /StructTreeRoot, Unmarked Pagination, and Broken Lists

  • What breaks: Legacy Word exports, scanned resolutions, or print-to-PDF outputs lack /MarkInfo << /Marked true >> and /StructTreeRoot, or leave running page numbers, headers, and decorative borders outside /Artifact containers. Screen readers announce repetitive footer text mid-sentence across every page break.
  • List normalization (<L>/<LI>/<Lbl>/<LBody>): Bullet lists converted from InDesign or Word frequently nest raw text runs directly inside <LI> without separating the bullet marker (<Lbl>) from the item body (<LBody>), triggering Clause 7.1 structural nesting failures.
  • Metadata & Viewer Preferences: PDF/UA-1 requires pdfuaid:part=1 in XMP metadata, synchronized document Info /Title and XMP dc:title, /ViewerPreferences << /DisplayDocTitle true >>, and a valid BCP-47 /Lang entry (e.g., en-US) on the document catalog.

2. Clause 7.3 & 7.18.5 — Missing <Figure> /Alt and Hyperlink /Contents

  • What breaks: Municipal seals, campus maps, and budget bar charts wrapped in <Figure> lack /Alt text (or lack /BBox attributes when non-inline). Hyperlink annotations (/Subtype /Link) require accessible /Contents descriptions so screen-reader link lists (NVDA + F7) convey destination context instead of repeating bare URLs.

3. Clause 7.5 — Budget & Fee Schedule Tables Missing <TH> Scope

  • What breaks: Financial tables exported from Excel or Word often tag every cell as <TD> or mark header cells as <TH> without /A << /O /Table /Scope /Column >> (or /Row), and omit RowSpan/ColSpan consistency across irregular header rows. Without explicit Scope or Headers/ID mapping, a screen reader reading page 14 of a fee schedule cannot announce which fiscal column a dollar figure belongs to.

4. Clause 7.18 — Interactive AcroForm /TU Tooltips, /OBJR, and /Tabs /S

  • What breaks: Fillable permit applications and enrollment forms routinely fail ISO 14289-1 Clause 7.18 because:
    • Widget annotations lack /TU (accessible user-prompt tooltip text—often defaulting to internal field names like txt_ap_14b),
    • The /StructTreeRoot lacks a <Form> structure element wrapping an /OBJR (Object Reference) pointing to the widget annotation,
    • The /ParentTree fails to map the widget's /StructParent integer back to that <Form> element, or
    • The page dictionary omits /Tabs /S (Structure tab order), causing keyboard Tab focus to jump erratically across columns.

5. Clause 7.21 — Subsetted Font /CIDSet Mismatches

  • What breaks: Many PDF generators emit inaccurate /CIDSet streams inside embedded Type0/CIDFont descriptors. While visually invisible, veraPDF and PAC 2026 reject /CIDSet bitmasks that fail to match embedded glyph IDs—requiring clean /CIDSet regeneration or removal per PDF/UA-1 font descriptor rules while preserving 100% visual glyph rendering.

Step-by-Step Verification Workflow ($0 Open-Source + Browser Check)

Before quoting or remediating a client's document library, establish an objective machine-validated baseline:

Option A: Zero-Retention Browser Validation (Mac, Linux, Windows)

Upload any PDF up to 20 MB (no account required, ephemeral temp validation deleted before the HTTP response returns):

Option B: Local veraPDF CLI Inspection

# Validate a candidate municipal or campus PDF against ISO 14289-1 (PDF/UA-1)
verapdf --flavour ua1 --format json permit-application.pdf > audit.json
Enter fullscreen mode Exit fullscreen mode

Option C: Automated GitHub Actions CI Gate (hadesloc/pdfua-ada-checker@v1)

Block inaccessible PDFs before they reach production web buckets by adding our official composite GitHub Action (release v1.0.0) to pull requests:

- name: PDF/UA-1 & ADA Title II Compliance Gate
  uses: hadesloc/pdfua-ada-checker@v1
  with:
    pdf-path: "public/documents"
    fail-on-violations: "true"
    max-files: "20"
Enter fullscreen mode Exit fullscreen mode

The action exposes total-pdfs, failing-pdfs, and failed-rules step outputs plus a per-file ISO 14289-1 summary table in $GITHUB_STEP_SUMMARY.

Pair machine validation (veraPDF XML / 0 failed structural rules) with your own internal team's Operator QA Checklist (OPERATOR-QA.md) before publishing:

  1. Press H in NVDA to confirm logical heading hierarchy (H1 -> H2 -> H3 without skipped levels).
  2. Press T to confirm <Table> header announcements across column/row navigation.
  3. Press K to confirm descriptive <Link> announcements.
  4. Press Tab across any fillable AcroForm fields to verify /TU prompt readout and visual reading sequence.

Pure-Software Scope & Integrity Notice: Automated software tools verify PDF structure and apply deterministic tagging/repair locally; OPERATOR-QA.md and manifest.json (human_review: "PENDING") are checklists for your own team's QA reviewer. Neither automated output nor templates constitute legal advice.


In-House Software Savings vs. Manual Outsourcing

Instead of outsourcing PDFs at industry manual per-page rates ($5.00–$15.00/page) or uploading sensitive public records to external portals, agencies and municipal teams can run PDF Accessibility Studio 100% locally on their own workstations with unlimited PDFs and pages:

  • PDF Accessibility Studio Solo ($9.50 USD w/ EARLY50, 50% off $19): Checkout on Gumroad — Full pdfa11y auto-tagging CLI, font CIDSet/ToUnicode repair, RapidOCR 3 Tr layer, local Web UI, GitHub Action CI gate, and OPERATOR-QA.md.
  • PDF Accessibility Studio Agency ($32.50 USD w/ EARLY50, 50% off $65): Checkout on Gumroad — Adds multi-folder batch runner, white-label HTML audit/ROI report generator, WordPress PDF Media Scanner, and browser extension.
  • PDF Accessibility Studio Commercial ($97.50 USD w/ EARLY50, 50% off $195): Checkout on Gumroad — Multi-seat internal CI/workflow commercial source license + all suites.
  • Free MIT CLI & Browser Tools ($0): Run npx --yes pdfua-ada-scanner@1.3.0 --help locally or use the calculator & free browser pre-checker on PDF/UA Partner Desk.

Top comments (0)