Corpus Assessment · WCAG Scorecard

Home project

Original uploads (v1) — before remediation

Point-in-time snapshot, as of October 4, 2026. This is a frozen record — the underlying corpus may have changed since. Assessed against the machine-verifiable checks under WCAG 2.1 AA + PDF/UA-1.

Status

Compliance posture

Compliance posture

0%compliant

0 of 86 scored documents · WCAG 2.1 AA

Documents
86
3,161 pages
Open violations
356
WCAG 2.1 AA
Failed
86
Needs review
0
Escalated
0

Progress

  • Blocked4
  • To fix82
  • To review0
  • Escalated0
  • Ready to approve0
  • Certified0
  • Analyzing0

Under Section 508 / ADA Title II, 86 of the 86 documents assessed here don't yet meet the accessibility bar — the 86 Failed plus the 0 Needs review, both of which block approval. The remaining checks break down by who clears each one — most of them without human input.

Standing

What stands open, and who owns it

Clears automatically — no human inputProof289
AI can draft — a reviewer acceptsYour reviewers13
Needs human confirmationYour reviewers34
Waits on a prerequisite (locked or blocked)Ockem20

Counts are open violations by who moves them next. This is standing, not sequencing — runs are planned and driven from the Automate surface.

By location

Exposure by site section

Violations and fixes rolled up by folder, mirroring the site. Expand a row to drill into the folders beneath it.

Site sectionStatusDocsFailedNeeds reviewCompliantAuto
clear		Pages affected
Forms & Permits
2525——60%15860
HR & Safety
1717——24%4476
census-briefs
55———57
demo
55——40%2160
Records Archive
2020——95%191,448
Reports & Publications
2222——9%2353
Unfiled
22———24

Scope

Coverage & methodology

Where these documents came from, and what they were checked against.

These 86 documents were added by direct upload — no site crawl seeded them. Every document was analyzed against the machine-verifiable checks under WCAG 2.1 AA + PDF/UA-1.

Per criterion

How the corpus scores, criterion by criterion

How many documents fail each WCAG success criterion — confirmed violations (red) vs. checks still needing human review (amber), ranked by how many documents they affect.

Confirmed violationsNeeds reviewWaits on tagging or OCRPassingNot applicable

33 checks. Every bar is scaled to the same 86 analyzed documents, so “71/86” reads as this check's share of the whole corpus; the muted remainder is documents the check doesn't apply to, and the chip names who clears it. Each criterion id links to the W3C's official definition of that rule — a document counts as failing only against the standard as written there. A check's page figure counts the pages of the documents it affects; a document usually fails several checks, so these are not additive — the corpus has 3,161 pages in total. The lighter amber is review that waits on tagging or OCR: those documents have no tag tree or no text layer yet, and the check rests on what that pass builds, so no one can make it until the pass runs. It still counts as pending.

Scope of these checks. This assessment covers the machine-verifiable WCAG 2.1 AA + PDF/UA-1 checks for documents. Between 14 and 39 of WCAG's 50 Level A/AA success criteria apply to any one PDF, depending on what it contains: links, form fields, scripts, media, or enough pages to need an outline. The rest govern pointer and motion input or multi-page site navigation that a document doesn't use. Proof evaluates every one of the 39 that can apply, by a machine check or a recorded attestation, and each document's certificate names how many apply to it and that every one of them was evaluated. A few that do apply — Images of Text, Resize Text, Sensory Characteristics and Use of Color — still need human judgment; where they apply they are counted in the Needs-review lane, never inflated into confirmed-violation counts. Criteria not named here are outside the scope of this assessment and are not claimed. This is not an implied full-conformance audit.