Inspectable source files beat generic case-study claims.
These examples show real source documents, the remediated structure, and the kind of dashboard evidence you should expect before trusting a remediation workflow.
A real document we processed
Below is an actual PDF that moved through the platform: the 2025 IRS Form 1040 — the U.S. Individual Income Tax Return millions of people fill out every year, and a textbook example of a complex government PDF: multi-column layout, dozens of form fields, checkboxes, dependent and income tables, and dense regulatory content all in one document.
As published by the IRS — image-rich form with no underlying structural tags. Screen readers can't navigate it; it reads as “image, image, image.”
After ADAComply: every element is tagged. H1/H2 headings, P paragraphs, Form fields, TR/TH/TD table cells — all present in the structure tree that screen readers actually use.
The 100% pass result refers to the automated checks represented in the sample report. Judgment-based items such as meaning, reading experience, and procurement criteria are handled through review when the workflow flags uncertainty.
What the 1040 example demonstrates
The live sample above is included so the source and remediated files can be inspected directly, with the actual output shown alongside the original.
- Form fields: visible labels need to become programmatic labels that assistive technology can announce.
- Tables: tax forms include row and column relationships that need proper table structure, not just visual alignment.
- Reading order: dense government forms need a logical sequence even when the visual layout is split across sections.
- Validation evidence: the output needs a repeatable report, not just a claim that the document was fixed.
How we approach a hard document
The pattern that runs through every case study above:
- Run 3,000+ checks. An average document can run more than 3,000 checks, while complex PDFs can run hundreds of thousands.
- Auto-fix what we can. Tagging, reading order, alt-text suggestions, OCR for scans, table structure, language metadata, font/Unicode mapping.
- Hand off the rest to specialists. The uncertain page where automation flags uncertain output goes to in-house specialists, included in the per-page price. Most often it's nuanced alt text or a table where automation can't infer the intended structure.
- Per-document report on every output. Every PDF stores a dashboard report listing what passed, what was fixed, and which standards ADAComply is designed to remediate PDFs to.
Run a free PDF audit on your own library.
Send us your website and we prepare a categorized PDF dashboard, free. You'll see what kind of remediation each document needs before you spend anything.
Get a Free PDF Audit