SYSTEM ONLINE · aws us-west-1 · build 26.04.2
POs & NET 30 accepted · 559-251-7767 · Fresno, CA
SentraCheck // document compliance
Login Request a Demo
[ ADA TITLE II · DOJ INTERIM FINAL RULE ]

Your accessibility deadline is April 26, 2027.

For entities serving 50,000+ residents

Every state and local government in the country must make its websites, apps, PDFs, and published documents WCAG 2.1 Level AA compliant — ADA Title II is federal, and it applies in all 50 states. Entities with 50,000+ population face an April 26, 2027 deadline, moved from the original April 24, 2026 cutoff. Smaller entities and special districts have until April 26, 2028. Smart agencies are using the extra time methodically — not to delay.

Request a Demo PERSONALIZED See the live scanner
§ 01 · Interactive

Watch the scanner work.

Drop a PDF on the left. Findings populate on the right in real time — mapped to WCAG 2.1 Level AA success criteria with severity, page reference, and remediation guidance.

scanner.live queue.tsv findings.json
SCANNING · WCAG 2.1 AA
FILE resolution-2026-014.pdf
SHA-256 9b1e…f7a4
PAGES 14 · 384 KB
RESOLUTION No. 2026-014
City of Sample · Adopted March 14, 2026
WHEREAS, the City Council finds that …
[image: city seal] — no alt text
… the public health, safety, and welfare …
NOW, THEREFORE, BE IT RESOLVED that the City
untagged structure · no heading hierarchy
Council of the City of Sample hereby adopts …
Section 1. The recitals set forth above …
contrast 3.1:1 — fails 1.4.3
Section 2. The City Manager is authorized …
// findings · WCAG 2.1 AA 3 critical · 4 serious · 2 minor
WCAG 1.1.1 Level A CRITICAL
Missing image alt text
p.1 · seal.png How to fix →
WCAG 1.3.1 Level A CRITICAL
Untagged PDF — no structure
document How to fix →
WCAG 1.4.3 Level AA SERIOUS
Contrast ratio 3.1:1 (need 4.5:1)
p.2 · §3 body How to fix →
WCAG 2.4.2 Level A SERIOUS
Document title set to filename
metadata How to fix →
WCAG 2.4.4 Level A MINOR
Vague link text — "click here"
p.4 How to fix →
Export findings VPAT · JSON · CSV
Δ 04:12:38 PDT region : us-west-1 engine : AI + rules retention : 0s (scan only)
Live capture · 29 accessibility checks · <10s typical single-page scan · WCAG 2.1 AA + Section 508 + PDF/UA
§ 02 · Coverage

Every WCAG 2.1 success criterion. Mapped, scored, exportable.

We map the WCAG 2.1 Level A/AA success criteria that apply to PDF and document accessibility, across the four POUR principles — 20 auto-detected, 6 flagged for manual review — plus PDF/UA-1 conformance. Findings are tagged with the exact criterion so your VPAT writes itself.

1
PERCEIVABLE
Information presentable to senses
12 / 19 auto-detected
✓1.1.1Non-text Content
◌1.2.xTime-based Media
✓1.3.1Info & Relationships
✓1.3.2Meaningful Sequence
◌1.4.3Contrast (Minimum)
✓1.4.4Resize Text
✓1.4.10Reflow
◌1.4.11Non-text Contrast
2
OPERABLE
UI components must be operable
11 / 20 auto-detected
✓2.1.1Keyboard
✓2.1.2No Keyboard Trap
✓2.4.2Page Titled
✓2.4.4Link Purpose (in Context)
✓2.4.6Headings and Labels
✓2.4.7Focus Visible
◌2.5.3Label in Name
◌2.5.4Motion Actuation
3
UNDERSTANDABLE
Information must be understandable
5 / 7 auto-detected
✓3.1.1Language of Page
✓3.1.2Language of Parts
✓3.2.1On Focus
✓3.2.2On Input
✓3.3.1Error Identification
◌3.3.2Labels or Instructions
4
ROBUST
Compatible with assistive tech
4 / 4 auto-detected
✓4.1.1Parsing
✓4.1.2Name, Role, Value
✓4.1.3Status Messages
✓PDF/UAISO 14289-1 conformance
✓  auto-detected by SentraCheck ◌  requires human review (DOJ explicitly notes automated tools cannot test for everything)
§ 02b · Policy controls

Set the bar your policy requires.

Some criteria — contrast, reading order, language of parts — Adobe Acrobat itself flags as requiring human verification. Your compliance team decides whether they should fail the document, warn, or stay advisory. SentraCheck lets you redefine severity per WCAG criterion or per individual rule, scoped to your company.

01

Per-criterion default

Pick a baseline severity for every finding under WCAG 1.4.3, 1.3.2, or any other criterion. Affects all rules that map to it.

scope=criterion
02

Per-rule override

Need finer control? Override an individual rule like ADA-LOW-CONTRAST while leaving the rest of the criterion at default. Per-rule wins over criterion default.

scope=rule
03

Audit trail

Every override stores who changed it and when. The full history is visible inline on the criterion page so your compliance team has a defensible record.

updated_by · updated_at
04

Future scans only

Overrides apply to the next scan onward. Historical scan records stay frozen — no compliance status flips retroactively, no audit headaches.

forward-only
↳  owners and admins can edit; everyone in the company can view ✓  severity counts, score, and pass/fail all use the overridden values
§ 03 · Conversion

From inaccessible PDF to WCAG 2.1 AA HTML — in one step.

Most agencies publish PDFs that are unreadable to screen readers. We rebuild the document as semantic HTML — headings, lists, tables, and alt text intact. Drag the slider to compare.

BEFORE · resolution-2026-014.pdf AFTER · resolution-2026-014.html
WCAG 2.1 AA · semantic HTML · screen-reader ready

Resolution No. 2026-014

City of Sample · Adopted March 14, 2026

WHEREAS, the City Council finds that the public health, safety, and welfare of the citizens require the adoption of this resolution;

alt: "Official seal of the City of Sample, established 1872"

Section 1. Recitals

The recitals set forth above are true and correct, and incorporated herein by reference.

Section 2. Authorization

The City Manager is hereby authorized to execute the agreements described herein…

0 → 100% SEMANTIC TAGGING
3.1 → 7.4 CONTRAST RATIO
4 → 4 HEADINGS · H1+H2
0 → 6 ALT TEXT BLOCKS
9.4s CONVERSION TIME
§ 04 · Auto-Remediation

Don't just find the issues. Fix them.

Upload a PDF and SentraCheck repairs the most common accessibility failures automatically — then hands it back ready to download. For every image, AI suggests alt text; you review and approve.

01 · UPLOAD
Drop in a PDF

Drag & drop any PDF. It's processed transiently and never stored — no document record, no retention.

02 · REVIEW
Approve the fixes

We auto-fix what we can and pre-fill AI alt text for each image. Edit any suggestion, or mark an image decorative.

03 · DOWNLOAD
Get the fixed file

Download a repaired PDF, ready to publish — usually in seconds. Re-scan to confirm the score jump.

✓Document title

Sets a descriptive title so the document is identifiable. WCAG 2.4.2.

✓Title shown in reader

Turns on DisplayDocTitle so readers show the title, not the filename. PDF/UA.

✓Document language

Sets the language so screen readers use correct pronunciation. WCAG 3.1.1.

✓Tab & reading order

Sets structure tab order on every page so AT navigates logically. WCAG 2.4.3.

✓Bookmarks & outline

Generates a navigable outline from the document's headings. WCAG 2.4.5.

✓Form field labels

Adds accessible names to unlabeled form fields. WCAG 1.3.1 & 4.1.2.

✓Link descriptions

Describes bare URL links so their purpose is announced. WCAG 2.4.4.

✓Image alt textAI

Claude vision drafts alt text for every image — you review, edit, or skip. WCAG 1.1.1.

Independently validated. Every remediated document is checked against ISO 14289-1 (PDF/UA-1) with veraPDF — the PDF Association's open-source conformance validator — and the verified result is shown on each scan. Automated validation covers the machine-checkable requirements; a human should still confirm alt-text quality and reading order.

Honest about the limits. OCR can misread text — no vendor's automation prevents that. We flag low-confidence pages for human review rather than publishing them silently (~8% of pages, in production). Alt-text quality still warrants a human check. And some PDFs exported from design software use font encodings we can't yet map reliably — we flag those rather than guess. Want HTML instead of a fixed PDF? Convert to fully tagged WCAG 2.1 AA HTML in one step (above) — better for reading on a phone, while the PDF remains the document of record.

Request a Demo PERSONALIZED
§ 05 · Scanned Documents

Scanned PDFs, made actually accessible.

Scanned pages are the dominant document type in a clerk's office — and the hardest to make accessible. Most tools describe the page as one long image caption. We give it a real text layer.

✓Real OCR text layer

Searchable, selectable, and navigable word by word — not a page-long alt-text description of the image. WCAG 1.1.1.

✓PDF/UA-1 verified

Every remediated scanned page is independently verified against ISO 14289-1 by veraPDF — not our own scoring.

✓Built for scale

Tested to 590 pages, resumable if interrupted, at roughly 2,400 pages/hour in production.

✓Low-confidence review

OCR misreads happen. Low-confidence pages are flagged for human review — never published silently.

✓Multilingual tagging

Per-paragraph language tagging for multilingual documents, so screen readers switch pronunciation correctly. WCAG 3.1.2.

// anyone can check it

A compliance claim you can prove wrong.

Every document we verify gets a certificate, and every certificate is tied to the SHA-256 of the exact file you publish. Change one byte and it stops matching — which is the point. The code travels in your export, so counsel, an auditor, or a resident who complained can check it without an account and without asking us.

✓Measured, not asserted

The certificate states what veraPDF measured against PDF/UA-1 (ISO 14289-1) on a named date — the failing clauses by number, not a grade we invented.

✓Or check the file itself

Drop the PDF on the verification page. It's fingerprinted in your browser and never uploaded — only the digest is sent — proving the file in hand is the one we verified.

✓Records the human part

veraPDF can confirm a description exists; only a person can confirm it's right. The certificate says how many were checked by a reviewer, and when.

Try the verification page →

From the blog

Related reading

Practical
WCAG 2.1 AA for Government PDFs: A Checklist
The 14 success criteria most agency PDFs fail and how to fix each one.
Strategy
PDF vs HTML for ADA Compliance
Both can meet WCAG 2.1 AA. Cost, ongoing burden, and user experience are dramatically different.
Reference
Section 508 vs WCAG 2.1 vs ADA Title II
A plain-English comparison of the three accessibility standards public agencies hear about most.
FREE · NO COMMITMENT

Find every accessibility issue in your entire document corpus.

Send us your published PDF library — in a live demo, we'll count every page, score it against WCAG 2.1 AA, and walk you through a remediation plan. Sized to your April 2027 deadline.

Request your demo
POs & NET 30 · 559-251-7767