SignalFeed.dev / Guides / Data

Title II PDF readiness: Hutchinson, Minnesota

Hutchinson must make its web content, including posted PDFs, meet WCAG 2.1 Level AA by April 26, 2028 under the ADA Title II web rule. Here is what an automated scan of https://hutchinsonmn.gov/ found.

Hutchinson: automated PDF checks, crawled 2026-11-19
MeasureResult
Title II compliance dateApril 26, 2028
Population (2020 Census)14,599
Site pages crawled182
PDF links found on those pages262
PDFs analyzed259
Tagged (have a structure tree)59.1%
Document language set50.6%
Document title set53.3%
Scanned (image-only pages)7.3%
Changed in 2024 or later (PDF date)37.1%
Passed veraPDF PDF/UA-10 of 20 tested
Estimated pages to remediate1,691

What stands out

Most PDFs we sampled have no tag structure. The quickest win is at the source: in Word, use real Heading styles and save with File > Save As > PDF > Options > “Document structure tags for accessibility” turned on. New agendas and notices then publish tagged instead of adding to the backlog.

Largest documents failing a basic check

These are examples, not a complete list.

Free sample

If this is useful, send us one public document from your site (an agenda, minutes, a budget or a report, not a completed form or anything holding personal information) and we will return 2 pages rebuilt as a tagged PDF with a veraPDF report, free. A person reviews every sample by hand before it goes back. Larger jobs are quoted only after we have reviewed the actual files, because scanned pages, complex tables and forms are priced separately.

Request a free 2-page sample

Method and limits

These are automated checks, not a legal finding and not a WCAG conformance test. In November 2026 a crawler identifying itself as SignalFeedReadinessBot visited up to 300 public HTML pages on each city's main website, obeying robots.txt and making at most one request per second. It collected PDF links on the same website and analyzed up to 400 of them (a random sample where more were found). It did not log in, submit forms, or get around any bot protection; a site that blocked or challenged it is reported as blocked.

For each PDF it recorded the page count, whether the file has a tag structure (a StructTreeRoot), whether a document language and title are set, and whether sampled pages have extractable text (pages that are images only are counted as scanned). Up to 20 PDFs per city were also run through veraPDF against PDF/UA-1, the machine-checkable part of PDF accessibility.

  • Passing these checks does not make a PDF accessible. Reading order, correct tags, table headers and image descriptions need a person.
  • Not every PDF must be fixed. The rule (28 CFR 35.201) has exceptions, including archived content kept only for reference and some preexisting documents. We cannot tell from the outside which files qualify.
  • Coverage is partial: 300 pages is not the whole site, and documents in agenda systems, third-party portals or other domains were not counted.
  • “Estimated pages to remediate” adds up the pages of sampled PDFs that fail at least one basic check (no tags, no language, or scanned) and scales that to all PDF links found. Treat it as an order of magnitude.

Corrections

If a number here is wrong, a document is exempt or already replaced, or you would like this page taken down, email aaron.signalfeed@gmail.com and we will correct or remove it.

All 20 Minnesota cities