How to fix an issue within the Structural Parent Tree for Accessiblilty

[MTUM02]

Looking for help: My PDF passed the Acrobat Accessibilty test but is not passing the PAC3 test for the following reasons which all fall within the Structural Parent Tree Section under the basic requriements (ISO 32000-1):

- Entry for given MCID missing

- Inconsistent entry found

There are several errors for each of these problems and when you click on the individual item, such as entry for given "MCID" missing, it doesn't show where the problem is occuring in the document like it usually does. In other words, typically when you click on an issue is points to where the problem is occuring. In this case it is just blank. How can I get rid of this issue so that the document passes?

Thanks so much!

[RachitJain]

Hi, 

Can you please share the document with me so that I can provide a fix for the issue.

Thanks 

Rachit

[Bevi Chagnon - PubCom.com]

Did you open the Results in Detail window in PAC 3? It's the top button in the lower left.

Only that windows takes you to the actual problem item.

[Kristine5F92]

Did you have a fix for this issue? I'm having the same problem with som PDF's

[a_C_student]

I've run into the Inconsistent Entry error a couple of times. After much trial and error, I think a found a fix - it is kinda goofy and I'm not sure it always works, but it worked for me both times. 

In the Page Thumbnails pane, select all the pages and Extract Pages as Seperate Files. Open the first page, then back in the Page Thumbnails pane, add all the other pages back in. Somehow deconstructing then reconstructing the PDF fixed the mystereous Inconsistent Entry error. 

Re. the "Entry for given MCID missing" error - I don't recall running into that one. Maybe cross your fingers and try this ...

• Tools - Print Production - Preflight.
• Make sure Acrobat Pro DC 2015 Profiles is selected in the Libraries window at the top
• Select the "Make individual corrections" tool (the wrench icon).
• Enter StructElem in the search field and carry out the correction "Insert missing Type entry in StructElem objects".

[KTdid.]

Yesss! I just ran into this for the first time. Thanks for the solution!

[Bevi Chagnon - PubCom.com]

No need to extract the PDF into separate files. That will cause more problems with internal hyperlinks, cross references, tables of content, and the overall tag tree itself.

Just run the Preflight steps mentioned above.

But remember that this is a band-aid. Best to figure out what you're doing wrong in InDesign. Usually it stems from incorrectly threaded story frames, inconsistent use of Paragraph Styles, and basic poor construction methods in InDesign.

[hilary2287 · Accepted solution]

@Bevi Chagnon - PubCom.com I'm having this issue and Preflight didn't fix it. As the OP stated, the Results in Detail pane doesn't show where the error is (screenshot attached). What can I do to locate the errors? This is a large document that passed all other criteria. Thank you.

[maxwithdax]

There are third-party tools that allow you to "Rebuild" the structural parent tree. Unfortunately, I have yet to find a solid solution using Acrobat alone.

[hilary2287]

@maxwithdax Is there a particular third-party tool that you recommend? Thank you!

[Chad Chelius]

axesPDF allows you to fix this error.

[Katarzyna20270147p0wv]

Hi, could you point out how this can be fixed in axesPDF? with what tool?

[Chad Chelius]

Click on the Logical Structure tab and click the Rebuild Structural Parent Tree button.

[Irasema21762708dln9]

See my previous reasponse, in my case I re-did my work because it was a small report. If you you really want to avoid redoing it, what I would do is split the pdf in smaller sections and check those until you narrow down which section has the error, once you narrow it down to a manageable section I would extract the pages individually until I find which page has the error and then I would re-pdf that page and get it to pass ADA and then reinsert it into the main report and fix any issues that page replacement generate. Not ideal but depending on the document size it might be worth it.

[Irasema21762708dln9]

I had this issue as well. Wasn't able to figure out how to fix. Preflight was not fixing it. Axes wanted a $650 subscription.

My report was small enough (50 pages), I retraced my steps, the original PDF did not have this error, the only thing I had done diffrently was to use Preflight to address the Metadata error (XMP, another know Adobe issue, unable to fix it either because every time I try to append with xmp file Adobe crashes). The second time around I did not use the Preflight, fixed Metadata errors manually, the only disadvantage was that Preflight was previously fixing "Alternative description missing for an annotation" automatically, I ended up having to fix 80+ of those errors manually. I know it's not a solution, just sharing that Preflight is what caused it in my file to begin with.

[maxwithdax]

Can I ask what extra data you are including in your XMP? just curious why people go that route rather than adjusting the properties in the file.

[Irasema21762708dln9]

I used the attached .xmp file that was recommend by Tagged PDF, they provided a link to download and it worked for a few years until Adobe decided to start crashing everytime I tried to append it.

[maxwithdax]

This is the old way to add the identifier. You can use the Preflight Fixup to add the identifier without the external XMP document. Print Production > Preflight > Set PDF/UA-1 entry.