# How to make a pdf document ada compliant for our reports? **URL:** \ **Category:** Optimize & Repair\ **Tags:** optimization\ **Created:** [October 29, 2026, 3:21pm UTC](https://community.pdfsuite.io/t/how-to-make-a-pdf-document-ada-compliant-for-our-reports/76 "2026-10-29T15:21:51Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![witty\_hawk](https://community.pdfsuite.io/letter_avatar_proxy/v4/letter/w/a88e4f/32.png) [@witty\_hawk](https://community.pdfsuite.io/u/witty_hawk)\ **Post date:** [October 29, 2026, 3:21pm UTC](https://community.pdfsuite.io/t/how-to-make-a-pdf-document-ada-compliant-for-our-reports/76/1 "2026-10-29T15:21:51Z")
I need our internal reports to be ADA compliant PDFs, but the accessibility check still fails on missing tags after I export from Word. Has anyone dealt with getting the reading order right? ---
**Author:** ![patient\_midnight](https://community.pdfsuite.io/user_avatar/community.pdfsuite.io/patient_midnight/32/25_2.png) [@patient\_midnight](https://community.pdfsuite.io/u/patient_midnight)\ **Post date:** [October 29, 2026, 3:21pm UTC](https://community.pdfsuite.io/t/how-to-make-a-pdf-document-ada-compliant-for-our-reports/76/2 "2026-10-29T15:21:54Z")
I ran into this with Word exports too. I had to tag the PDF, set the document language and title, then check the reading order manually, especially around tables, headings, and images. If it still fails, try opening the PDF in Adobe Acrobat’s accessibility checker since Word’s export usually misses some tags. ---
**Author:** ![guest.238671](https://community.pdfsuite.io/user_avatar/community.pdfsuite.io/guest.238671/32/38_2.png) [@guest.238671](https://community.pdfsuite.io/u/guest.238671)\ **Post date:** [October 31, 2026, 10:43am UTC](https://community.pdfsuite.io/t/how-to-make-a-pdf-document-ada-compliant-for-our-reports/76/3 "2026-10-31T10:43:06Z")
In Word, use the built in Heading styles for titles and section headers before you export, that usually fixes most tag and reading order problems. Also check your tables have header rows marked, that trips people up a lot. What version of Word are you on? ---
**Author:** ![gaa\_miami](https://community.pdfsuite.io/user_avatar/community.pdfsuite.io/gaa_miami/32/39_2.png) [@gaa\_miami](https://community.pdfsuite.io/u/gaa_miami)\ **Post date:** [October 31, 2026, 7:43pm UTC](https://community.pdfsuite.io/t/how-to-make-a-pdf-document-ada-compliant-for-our-reports/76/4 "2026-10-31T19:43:10Z")
When you export from Word, click Options in the Save As dialog and make sure ‘Document structure tags for accessibility’ is checked. Also make sure you use proper Heading styles in Word rather than manual bolding. That usually fixes the tags and sets the reading order correctly. ---
**Author:** ![baking\_addict](https://community.pdfsuite.io/user_avatar/community.pdfsuite.io/baking_addict/32/28_2.png) [@baking\_addict](https://community.pdfsuite.io/u/baking_addict)\ **Post date:** [November 1, 2026, 8:13am UTC](https://community.pdfsuite.io/t/how-to-make-a-pdf-document-ada-compliant-for-our-reports/76/5 "2026-11-01T08:13:52Z")
First thing I’d check is Word’s own Accessibility Checker before exporting, especially headings and alt text. When you Save As PDF, hit Options and tick “Document structure tags for accessibility” so the tags actually come through. Reading order usually follows the order things were placed, so text boxes and floating images are the usual culprits, try anchoring them inline. Keep a backup of the original before you fiddle. ---
**Author:** ![distracted\_hunter](https://community.pdfsuite.io/user_avatar/community.pdfsuite.io/distracted_hunter/32/29_2.png) [@distracted\_hunter](https://community.pdfsuite.io/u/distracted_hunter)\ **Post date:** [November 1, 2026, 8:28pm UTC](https://community.pdfsuite.io/t/how-to-make-a-pdf-document-ada-compliant-for-our-reports/76/6 "2026-11-01T20:28:37Z")
Word exports always leave tags messy for me. I open the file in PDFcap and add the missing tags, then drag the reading order into the right sequence. That’s the easiest way I’ve found. Avoid relying only on the Word export or the check will keep failing. Not sure if it’s the same on Mac. ---
**Author:** ![dark\_frost](https://community.pdfsuite.io/user_avatar/community.pdfsuite.io/dark_frost/32/40_2.png) [@dark\_frost](https://community.pdfsuite.io/u/dark_frost)\ **Post date:** [November 2, 2026, 11:58pm UTC](https://community.pdfsuite.io/t/how-to-make-a-pdf-document-ada-compliant-for-our-reports/76/7 "2026-11-02T23:58:07Z")
Start in Word by using real heading styles, table headers, alt text, and simple lists before exporting. That gave me much better tags than trying to fix everything afterward. For reading order, I check the PDF with a screen reader or its accessibility checker, especially around tables, text boxes, and charts. Decorative items should be marked as decorative, while meaningful charts need a short description. ---
**Author:** ![chess\_addict](https://community.pdfsuite.io/user_avatar/community.pdfsuite.io/chess_addict/32/31_2.png) [@chess\_addict](https://community.pdfsuite.io/u/chess_addict)\ **Post date:** [November 4, 2026, 4:58am UTC](https://community.pdfsuite.io/t/how-to-make-a-pdf-document-ada-compliant-for-our-reports/76/8 "2026-11-04T04:58:08Z")
Had the same issue with a family tax report. In Word, I used proper heading styles and table headers, then exported with “Document structure tags for accessibility” enabled rather than printing to PDF. Afterward, I corrected the Tags panel and Reading Order tool, marking decorative items as artifacts. The checker can still miss context, so I also tested keyboard navigation and read it through with NVDA. ---
**Author:** ![WittyComet](https://community.pdfsuite.io/user_avatar/community.pdfsuite.io/wittycomet/32/41_2.png) [@WittyComet](https://community.pdfsuite.io/u/WittyComet)\ **Post date:** [November 5, 2026, 10:13am UTC](https://community.pdfsuite.io/t/how-to-make-a-pdf-document-ada-compliant-for-our-reports/76/9 "2026-11-05T10:13:13Z")
we hit this with our intake forms. fix it in word first: real heading styles, alt text on images, and tick the document structure tags option when saving. for stubborn reading order stuff, acrobat pro has a reading order tool to fix the tag tree manually. ---
**Author:** ![orla\_ward](https://community.pdfsuite.io/user_avatar/community.pdfsuite.io/orla_ward/32/33_2.png) [@orla\_ward](https://community.pdfsuite.io/u/orla_ward)\ **Post date:** [November 6, 2026, 6:13pm UTC](https://community.pdfsuite.io/t/how-to-make-a-pdf-document-ada-compliant-for-our-reports/76/10 "2026-11-06T18:13:34Z")
@distracted_hunter I had the exact same tagging issue when a submission portal rejected my thesis. My old laptop would freeze whenever I tried fixing the reading order after exporting. I found it easier to just strip out all floating objects in Word first. Dragging tags around in PDFcap is fine if you have the patience. ---
**Author:** ![godTitan](https://community.pdfsuite.io/user_avatar/community.pdfsuite.io/godtitan/32/42_2.png) [@godTitan](https://community.pdfsuite.io/u/godTitan)\ **Post date:** [November 7, 2026, 11:13pm UTC](https://community.pdfsuite.io/t/how-to-make-a-pdf-document-ada-compliant-for-our-reports/76/11 "2026-11-07T23:13:21Z")
@distracted_hunter honestly i tried pdfcap for my menus but i usually just fix the order right in word. to be fair it saves me from doing the same manual tag fixes every time i update prices and export again. ---
**Author:** ![raptorsfan](https://community.pdfsuite.io/user_avatar/community.pdfsuite.io/raptorsfan/32/35_2.png) [@raptorsfan](https://community.pdfsuite.io/u/raptorsfan)\ **Post date:** [November 11, 2026, 6:43am UTC](https://community.pdfsuite.io/t/how-to-make-a-pdf-document-ada-compliant-for-our-reports/76/12 "2026-11-11T06:43:11Z")
Yeah version matters more than people think, @guest.238671. I’m on 365 and the header row tagging still gets missed half the time even with built in styles. I just double check it in the Tags panel after export instead of trusting Word alone.