Skip to main content
Inspiring
June 10, 2021
Answered

Accessible Document Failed Accessibility Checker (Content Placed from Word)

  • June 10, 2021
  • 2 replies
  • 643 views

I have built a completely accessible publication using the same process I have used countless times. The only thing I have done differently is import content from Word.  The content I imported from Word was completely accessible as well and I mapped the Heading styles I used there to the Paragraph styles used in InDesign.  Every image is alt-tagged.  Every decorative item is marked as an artifact.  Every paragraph style is mapped to a PDF export tag with the appropriate heading level.  All headings are used correctly and in the appropriate order.  I have no tables.  
 
The Acrobat accessibility checker is making all sorts of wild claims.  It's failing all of my alt-tags.  It is insisting I have tables and I don't.  It's saying I have no tab structure and I do.  It says my headings are nested inappropriately.  
 
Is there some nonsense hiding somewhere in this document from Word that is causing this to fail?  How do I remove it?  This is due tonight and I have used this exact process over and over before without issue.  The only thing I did differently was Place content from word directly into the InDesign file.
 
I rebuilt the entire document and it passes the accessibility checker without issue.  I suspect these errors are due to having placed content from Word into my InDesign file (and possibly mapping styles from Word to those used in ID) but I would like to know why this exploded as it did. 

Thanks!

This topic has been closed for replies.
Correct answer Bevi Chagnon - PubCom.com
quote

The Acrobat accessibility checker is making all sorts of wild claims.

By @bren87

 

We'll need more details from you to figure out what's happening.

  • Can you post the report from Acrobat's Accessibilitiy Checker?
  • Which version of Acrobat are you using? (Give the build number)
  • Mac or PC?
  • Show us a screen capture of your tag tree that shows where it's correct so that we can correlate that with the checker's report.

 

--Bevi

2 replies

Bevi Chagnon - PubCom.com
Legend
June 10, 2021
quote

The Acrobat accessibility checker is making all sorts of wild claims.

By @bren87

 

We'll need more details from you to figure out what's happening.

  • Can you post the report from Acrobat's Accessibilitiy Checker?
  • Which version of Acrobat are you using? (Give the build number)
  • Mac or PC?
  • Show us a screen capture of your tag tree that shows where it's correct so that we can correlate that with the checker's report.

 

--Bevi

|    Bevi Chagnon   |  Designer, Trainer, & Technologist for Accessible Documents ||    PubCom |    Classes & Books for Accessible InDesign, PDFs & MS Office |
bren87Author
Inspiring
June 10, 2021

I have built a completely accessible publication using the same process I have used countless times. The only thing I have done differently is import content from Word.  The content I imported from Word was completely accessible as well and I mapped the Heading styles I used there to the Paragraph styles used in InDesign.  Every image is alt-tagged.  Every decorative item is marked as an artifact.  Every paragraph style is mapped to a PDF export tag with the appropriate heading level.  All headings are used correctly and in the appropriate order.  I have no tables.  

The Acrobat accessibility checker is making all sorts of wild claims.  It's failing all of my alt-tags.  It is insisting I have tables and I don't.  It's saying I have no tab structure and I do.  It says my headings are nested inappropriately.  

Is there some nonsense hiding somewhere in this document from Word that is causing this to fail?  How do I remove it?  This is due tonight and I have used this exact process over and over before without issue.  The only thing I did differently was Place content from word directly into the InDesign file.

bren87Author
Inspiring
June 10, 2021

I rebuilt the entire document and it passes the accessibility checker without issue.  I suspect these errors are due to having placed content from Word into my InDesign file (and possibly mapping styles from Word to those used in ID) but I would like to know why this exploded as it did.  Thanks.