The seven steps, if you want to try.
This is the real checklist, the same one accessibility auditors work from. Nothing here is withheld. Work through it and you will have a genuinely better document than you started with.
- Tag the structure. Headings, paragraphs, lists and tables must be marked as what they are, not just styled to look like it. Untagged text is a wall of characters to a screen reader.
- Set the reading order. Visual order and tag order are different things. A two-column layout often reads straight across both columns unless you fix it by hand.
- Write alt text for every image. Decorative images get marked as artifacts so they are skipped entirely.
- Label every form field. Each field needs a name and a tooltip. Unlabelled fields are announced as “edit text” with no clue what belongs in them.
- Declare the document language and title. Without a language, screen readers guess the pronunciation. Without a title, the tab and the file are anonymous.
- Check color contrast. WCAG 2.1 AA wants 4.5:1 for body text. Scanned or design-locked documents usually miss it.
- Test it with an actual screen reader. Not a checker. JAWS or VoiceOver, and ideally someone who uses one daily.
Now the part most guides leave out: step seven is where it falls apart. Every PDF we have taken through all seven steps still failed on JAWS somewhere, usually in the form fields. That is not a skill problem. Read on.
We tried to make PDFs pass.
Nothing passed.
This page used to stop at the checklist above. Tutorials, video walkthroughs, the whole PDF-tagging playbook, and nothing after it. What follows is what we learned when we tested the results. After years of compliance work for county offices, townships, villages and small businesses, the verdict was unavoidable: PDFs do not reliably pass the standards the DOJ now expects.
Even tagged, the same PDFs failed axes4. Even fixed, JAWS users couldn’t complete the forms. The format itself was the problem.
Test your own PDFs on the same checker we used.
Upload any of your fillable forms to axes4’s free online accessibility checker — the same tool accessibility auditors use. See whether your PDFs actually PASS the compliance rules, or fail like everyone else’s.
Test a PDF on axes4 (opens in a new tab on an external site — axes4 is a third-party tool not maintained by Web Chick, and its accessibility cannot be guaranteed)You’ll leave webchick.com and open axes4.com in a new tab. axes4 is a third-party tool — we can’t guarantee the testing site’s own accessibility.
PDFs were designed for fixed-page print fidelity, not for assistive technology. The accessibility tree screen readers depend on doesn’t live cleanly inside a PDF. Tags break across readers. Form fields lose their labels. Reading order drifts. Even paid tagging tools produce documents that flunk axes4 (axesPDF) testing — the gold-standard PDF accessibility checker.
So we stopped trying to patch a broken format and started converting PDFs to HTML. With HTML, we control every element of the code, name every label, define every reading order, and test the result against the same screen readers our clients’ users actually rely on.
How PDF to HTML conversion works.
Every fillable PDF is rebuilt from the ground up — not auto-converted by a script, not run through a tool. Hand-coded HTML/CSS, structured for WCAG 2.1 AA and Section 508, then tested with the people and software the law is meant to protect.
Audit the original PDF
We map every field, label, signature line, and dependent logic in the original document so nothing gets lost in the rebuild.
Rebuild as hand-coded HTML
Semantic HTML5, proper labels, ARIA where needed, full keyboard support. No frameworks, no auto-converted junk — clean code we can defend.
Test with real assistive tech
JAWS, VoiceOver, and a legally blind assistant walk through every form before delivery. If they can’t complete it, neither can your residents.
Three layers of accessibility testing.
No shortcuts.
Automated checkers catch the obvious mistakes — they miss everything else. Every Web Chick HTML conversion is validated by humans and by the screen readers your users actually run.
Legally blind assistant
Every converted form is walked through by an actual screen-reader-dependent user. Real keystrokes, real navigation, real feedback before anything ships.
VoiceOver
Built-in Apple screen reader testing on both desktop and mobile. We verify reading order, focus management, field labels, and error announcements.
JAWS
The industry-standard screen reader for accessibility audits. Final verification that the form meets WCAG 2.1 AA, Section 508, and DOJ ADA Title II expectations.
Free for simple PDFs.
$75 for fillable forms.
Most county and township informational documents — brochures, minutes, public notices — convert at no charge as part of our web work. The $75 fee applies only to fillable forms (applications, permits, public records with form fields). Most fillable forms are under three pages.
What’s included
- Hand-coded HTML/CSS rebuild of the PDF form
- WCAG 2.1 AA & Section 508 structured markup
- Keyboard-accessible form fields with proper labels
- Testing with axes4-equivalent automated checks
- JAWS & VoiceOver verification
- Walk-through with a legally blind assistant
- Submit-by-email or save-as-PDF on completion (your choice)
Simple text PDFs converted free when we're doing your web work — informational documents, brochures, meeting minutes, public notices. Longer or more complex fillable documents are quoted individually. Bulk pricing available for agencies converting whole document libraries.
Don’t wait until April 2027.
After the April 2026 interim final rule, the DOJ extended the ADA Title II web compliance deadlines — but the obligation didn’t change, only the runway. Agencies converting now have a clean handoff. The rest will be racing the clock with hundreds of forms and a queue of vendors who won’t answer the phone.
Start the conversation →PDF to HTML conversion, answered.
Can a PDF be made fully ADA and WCAG compliant?
In practice, no. Even properly tagged PDFs consistently fail accessibility testing tools like axes4 (axesPDF) and break down for real users on JAWS and VoiceOver. After years of testing, the reliable path to DOJ ADA Title II and Section 508 compliance for forms and documents is converting them to accessible HTML, where the code can be fully controlled and tested.
Why do PDFs fail ADA compliance testing?
PDFs were designed for fixed-page print fidelity, not for assistive technology. Tag structures break across PDF readers, form fields lose labels, reading order fails, and even paid tagging tools produce documents that fail axes4 testing and confuse JAWS, NVDA, and VoiceOver users. The format itself isn’t built for the accessibility tree screen readers depend on.
What is PDF to HTML conversion?
PDF to HTML conversion is the process of rebuilding an inaccessible PDF — especially fillable forms, applications, permits, and public records — as hand-coded HTML that meets WCAG 2.1 AA and Section 508. The HTML version is tested with JAWS, VoiceOver, and a legally blind assistant to confirm real-world accessibility before delivery.
How much does PDF to HTML conversion cost?
Simple text PDFs (informational documents, brochures, meeting minutes, public notices) are converted at no charge as part of our web work. Fillable PDF forms (applications, permits, public records with form fields) are $75 per form, up to 3 pages. Longer or more complex documents are quoted individually. Every conversion includes JAWS, VoiceOver, and screen-reader-user testing.
When is the DOJ ADA Title II web compliance deadline?
Following an April 2026 interim final rule, public entities serving 50,000+ must comply by April 26, 2027, and smaller entities and special districts by April 26, 2028. The compliance obligation didn’t change — only the runway.
What about scanned or image-based PDFs?
Scanned PDFs are the worst-case scenario for accessibility — they’re effectively pictures of text with no readable structure at all. Conversion is the only realistic path. We run OCR to extract the content, then rebuild it as semantic HTML.
Do I still need the original PDF after conversion?
Yes — many agencies keep the original PDF available as a print-friendly download alongside the accessible HTML form. The HTML version satisfies ADA Title II; the PDF stays available for users who prefer to print and complete by hand.
Can Web Chick host the converted forms?
Yes. If we built or maintain your website, the converted HTML forms are integrated directly into your site as part of the conversion fee. If we’re only doing the conversion, you receive the HTML file ready to deploy on your existing host.