Skip to main content
M
Matthew25488204sxya
Participant
August 11, 2022
Answered

Character Styles Break Tag/Container Structure on Export (Accessibility)

  • August 11, 2022
  • 4 replies
  • 835 views

I'm trying to export a PDF from Indesign accessibly. 
Apparently, any character style change in the middle of a paragraph (for example, this bold text here), breaks the tag container structure when viewed in Acrobat (see below).

 

 

The top line should read as a single line in a screen reader, but instead is being broken into three lines by the change in character style. My readers tell me this is not accessible, but there appears to be no way to fix it. I've bolded this text in InDesign in every way I can, I've triple-checked that it's export-tagged correctly, etc. etc., but Indesign refuses to make this read as a single line.
If there's no way to export correctly, is there a way to merge tag containers in Acrobat Pro to clean up Indesign's mess?

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

This list of errors from Acrobat's Preflight are different from what you originally posted, about individual tags being broken into multiple content container boxes.

 

Going down the error list in your last screen capture from Acrobat's Preflight, the errors are, starting with"Content neither..."

  • Every piece of content in a PDF must either be taggged or be designated by you as an artifact. Your PDF has content that is in "limbo," neither tagged nor artifacted. Correct this error in InDesign.
  • You have an incorrectly made hyperlink. Did you use InDesign's Hyperlinks panel and tools to generate your hyperlinks? (Both external to URLs and internal as cross-references.) Do you have hyperlinks on Parent Pages (master pages), such as in headers or footers that are automatically artifacted?
  • The PDF/UA identifier can only be built into a PDF that passes this Preflight test, so the errors must be corrected, and then you can apply the identifier to the file in Acrobat.
  • Display DocTitle is your control in Acrobat File/Properties/Initial View. And this requires that your file's XMP metadata for the Title field is complete, too.
  • The next 2 about forms fields and their annotations mean that the file has form fields but they weren't correctly made and tagged.
  • The last one about CIDset means that either 1) you didn't embed the fonts into the PDF when you exported it, or 2) your font doesn't contain one or more specific characters. Are all of your fonts OpenType (Unicode)? Unicode is required for accessibility.

 

Without seeing your PDF, It looks like you attempted to make an InDesign layout with form fields or other interactive elements in it, but didn't create them correctly. Also many basic InDesign requirements are missing, too, like fonts.

 

I suspect that good courses in basic InDesign and accessibility in InDesign would help you clear up these issues. InDesign is a pro-quality software program and requires training to correctly make files. If you want interactivity or accessibility, that requires specific additional training to have those features.

 

4 replies

Bevi Chagnon - PubCom.com
Bevi Chagnon - PubCom.com
Legend
September 12, 2022

Returning to the original poster's question:

 

quote

Apparently, any character style change in the middle of a paragraph (for example, this bold text here), breaks the tag container structure when viewed in Acrobat (see below).

 

 

The top line should read as a single line in a screen reader, but instead is being broken into three lines by the change in character style. My readers tell me this is not accessible, but there appears to be no way to fix it.

By @Matthew25488204sxya

 

What software are your readers using? Need software name, version, and platform.

 

If they are using JAWS or NVDA — the 2 leading screen readers in the industry — the multiple content containers (yellow boxes in the tag tree) do not affect how the content is voiced. And the multiple containers SHOULDN'T affect accessibility. 

 

We find the problem of either pauses/stops when non-compliant screen readers are used, such as Apple Preview (Mac) and Acrobat's built-in Read Aloud utility. Neither is a bonfide compliant screen reader (they're called text-to-speech utilities rather than screen readers).

 

|    Bevi Chagnon   |  Designer, Trainer, & Technologist for Accessible Documents ||    PubCom |    Classes & Books for Accessible InDesign, PDFs & MS Office |
D
defaultrvfqlsd4fwvj
Participant
September 10, 2022

I'm having the same frustrating issue and my pre-flight panel shows ZERO errors

Frans v.d. Geest
Community Expert
Frans v.d. GeestCommunity Expert
Community Expert
August 11, 2022

It is not broken up, it is all in the one <p> tag. InDesign has some strange things sometimes (with way to many <Span>) but this should be fine. If it is not accessible there is probably a complete other reason. Did you run the pdf/ua preflight check and error fixing in Acrobat? (Under Preflight panel, pdf standards, pdf/ua).

M
Matthew25488204sxyaAuthor
Participant
August 11, 2022

Well the Preflight check is telling me everything is wrong...

 

Meanwhile, the accessibility check is telling me everything is fine.

The whole document is readable and has a logical structure otheriwse, the screen readers just keep stopping whenever they hit a bold word.

We're testing with JAWS and NVDA

Bevi Chagnon - PubCom.com
Bevi Chagnon - PubCom.comCorrect answer
Legend
August 12, 2022

This list of errors from Acrobat's Preflight are different from what you originally posted, about individual tags being broken into multiple content container boxes.

 

Going down the error list in your last screen capture from Acrobat's Preflight, the errors are, starting with"Content neither..."

  • Every piece of content in a PDF must either be taggged or be designated by you as an artifact. Your PDF has content that is in "limbo," neither tagged nor artifacted. Correct this error in InDesign.
  • You have an incorrectly made hyperlink. Did you use InDesign's Hyperlinks panel and tools to generate your hyperlinks? (Both external to URLs and internal as cross-references.) Do you have hyperlinks on Parent Pages (master pages), such as in headers or footers that are automatically artifacted?
  • The PDF/UA identifier can only be built into a PDF that passes this Preflight test, so the errors must be corrected, and then you can apply the identifier to the file in Acrobat.
  • Display DocTitle is your control in Acrobat File/Properties/Initial View. And this requires that your file's XMP metadata for the Title field is complete, too.
  • The next 2 about forms fields and their annotations mean that the file has form fields but they weren't correctly made and tagged.
  • The last one about CIDset means that either 1) you didn't embed the fonts into the PDF when you exported it, or 2) your font doesn't contain one or more specific characters. Are all of your fonts OpenType (Unicode)? Unicode is required for accessibility.

 

Without seeing your PDF, It looks like you attempted to make an InDesign layout with form fields or other interactive elements in it, but didn't create them correctly. Also many basic InDesign requirements are missing, too, like fonts.

 

I suspect that good courses in basic InDesign and accessibility in InDesign would help you clear up these issues. InDesign is a pro-quality software program and requires training to correctly make files. If you want interactivity or accessibility, that requires specific additional training to have those features.

 

|&nbsp;&nbsp;&nbsp;&nbsp;Bevi Chagnon &nbsp;&nbsp;|&nbsp;&nbsp;Designer, Trainer, &amp; Technologist for Accessible Documents ||&nbsp;&nbsp;&nbsp;&nbsp;PubCom |&nbsp;&nbsp;&nbsp;&nbsp;Classes &amp; Books for Accessible InDesign, PDFs &amp; MS Office |
Bevi Chagnon - PubCom.com
Bevi Chagnon - PubCom.com
Legend
August 11, 2022

Actually your screen capture shows the file correctly tagged per the PDF/UA-1 standard. And the tag tree might have a <Span> tag around the bolded text, as well.

 

InDesign always breaks up tags into one or more yellow container boxes (they're not tags) based on the actual line breaks and formatting within the paragraph. But those multiple containers should not affect how the file is voiced  -- if you're using a PDF/UA-compliant screen reader, that is, and one that is relatively up to date.

 

What screen reader or text-to-speech assistive technology are you using? And on which platform?

 

|&nbsp;&nbsp;&nbsp;&nbsp;Bevi Chagnon &nbsp;&nbsp;|&nbsp;&nbsp;Designer, Trainer, &amp; Technologist for Accessible Documents ||&nbsp;&nbsp;&nbsp;&nbsp;PubCom |&nbsp;&nbsp;&nbsp;&nbsp;Classes &amp; Books for Accessible InDesign, PDFs &amp; MS Office |
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices