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.
Most guides stop here, and most PDFs still fail. The steps are right, but the checker also looks at details the steps don’t mention. The flowchart and gotchas below are what moved our PDFs from fail to pass.
From PDF to PDF/UA + WCAG pass.
Follow it top to bottom. Each question sends you down one path, and every path ends at the same two tests.
-
Question
Is it a fillable form?
Yes
Build an accessible HTML version first. Then give the PDF real fillable fields, each with a spoken name (tooltip) that says what goes in it. Blank lines on paper don’t count.
No
Brochure, flyer, report, notice or minutes. Go to the next question.
-
Question
Do you have the original file (Word, InDesign, Publisher)?
Yes
Fix it there: real heading styles, real lists and tables, alt text on pictures, a document title and language. Export with “Create tagged PDF” turned on.
No
Tag the PDF itself. If it is a scan, run text recognition (OCR) first, or the text isn’t there to tag.
-
Step
Tag everything, skip the decoration
All text, pictures and tables sit inside tags. Borders, background shapes, clip art and page numbers are marked as artifacts so screen readers skip them.
-
Step
Set the reading order
Put the tags in the order a person should read, panel by panel on a brochure. Headings in order, one main title, no skipped levels.
-
Step
Pictures: alt text and a position
One plain sentence saying what each picture shows, plus its bounding box (where it sits on the page). Missing positions fail every picture.
-
Question
Is any text printed on top of a photo?
Yes
The checker can’t see photo colors and fails the contrast. Put that wording in the photo’s alt text and mark the overlaid text as decoration, or give the text a solid color band.
No
Check that ordinary text meets 4.5:1 contrast and move on.
-
Step
Title, language, fonts
Document title shows in the title bar (not the file name), language set to English, every font embedded so text copies out as real letters.
-
Test 1
Run it through axesCheck. Both green?
No
Find the failing category in the table below, fix it and run it again.
Yes
PDF/UA: Fulfilled and WCAG: Fulfilled. Go to Test 2.
-
Test 2
Listen to it with a screen reader
NVDA is free, VoiceOver is built into every Mac and iPhone. The checker covers the rules a machine can verify. Listening tells you whether the reading order and alt text make sense to a person.
-
Green and green. Upload it.
Our axesCheck result, October 30, 2026.
What each failure usually means.
axesCheck shows counts, not explanations. These are the usual causes behind each line, from our own failed runs.
| axesCheck line | Usual cause | Fix |
|---|---|---|
| “The PDF does not contain a tag structure” | Exported without tags, or scanned | Export again with tagging on, or tag the PDF (OCR scans first) |
| 1.1 Text Alternatives | A picture with no alt text | Add alt text, or mark the picture as decoration |
| 1.3 Adaptable / Structure Elements | Pictures without a bounding box, or headings, lists and tables that aren’t tagged as such | Give every picture its position; tag real headings, lists and table headers |
| 1.4 Distinguishable | Low contrast, very often text printed on a photo | Move that text into the photo’s alt text, or put it on a solid color |
| 2.4 Navigable | File name shows instead of the title | Set the document title and “show title”; add bookmarks on long documents |
| 3.1 Readable | No language set | Set the document language |
| 4.1 Compatible | Form fields without names, or tags nested the wrong way | Give every field a tooltip; fix the tag nesting |
Gotchas that trip people up
- Hyphenated line breaks. “daugh-ter” across two lines can be read aloud as two broken words unless it’s tagged to read as one.
- Pictures of words. A title made as an image needs alt text with the exact words.
- Decoration left in. An untagged border or background shape is enough to fail PDF/UA.
- Checker green isn’t the finish line. It means the machine-checkable rules pass. Listen to it before you call it done.
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, so we can’t guarantee the testing site’s own accessibility.
Would rather hand it off? We tag brochures and documents so they pass, and for fillable forms we build an accessible HTML version as well, because it is the easiest for screen-reader users to complete.
How PDF to HTML conversion works.
Every fillable PDF is rebuilt from the ground up. It isn’t auto-converted by a script or run through a tool. We hand-code the HTML/CSS, structure it for WCAG 2.1 AA and Section 508, then test it 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 and no auto-converted junk, just 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, but 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 PDF check.
$75 for fillable forms.
We’ll test your PDFs for free and show you exactly what fails. For existing Web Chick clients, every PDF we post for you is made accessible as part of your service. Fillable forms are the exception, at $75 per form (applications, permits and other forms with 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)
The PDF accessibility check is free. We test your PDFs and show you what fails. Existing Web Chick clients get every PDF we post made accessible as part of their service, except fillable forms, which are $75 per form. For everyone else, fillable PDF forms are $75 per form (up to 3 pages), and simple text PDFs and longer documents are quoted individually. Bulk pricing is 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 did. 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?
Yes. As of October 2026 our PDFs pass both PDF/UA and WCAG (Level A and AA) on axes4’s axesCheck. It takes complete tagging: every image with alt text and a bounding box, decoration marked as artifacts, a correct reading order, real headings, lists and tables, embedded fonts, a title, a language setting and care with text printed over photos. A checker pass covers the machine-verifiable rules only, so we also test with screen readers. For fillable forms, an accessible HTML version is still the easiest for screen-reader users to fill in, so we offer both.
Why do PDFs fail ADA compliance testing?
Most fail on a few things: no tags at all, images without alt text or without a bounding box, decorative shapes left untagged, headings and lists that are only styled to look like headings and lists, a missing title or language, form fields without names and text printed over photos that checkers measure as a contrast failure. Fix those and most PDFs move from fail to pass. The table above lists what each axesCheck line usually means.
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?
The PDF accessibility check is free. We test your PDFs and show you what fails. Existing Web Chick clients: every PDF we post for you is made accessible as part of your service. Fillable forms are the exception, at $75 per form. Everyone else: fillable PDF forms (applications, permits and other forms with fields) are $75 per form, up to 3 pages. Simple text PDFs and longer documents are quoted individually, and bulk pricing is available for agencies. 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 did.
What about scanned or image-based PDFs?
Scanned PDFs are the worst-case scenario for accessibility, because 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.
