Im having the same problem. Can adobe provide a response to this?
Can you show us a link which fails? Because UA checking is very restrictive, not every link which is working is allowed to use in PDF/UA.
It is failing for me on TOC and Index entries.
Work that one out!
I am also having this issue. This is extremely aggravating if required to pass all checks for Section 508 as required by the federal government!
It's not only this issue. I find that the "articles" palette is a bad joke. It simply doesn't set the reading order, as promised. I need to use a third party plug-in called Frame Reporter to manually put each item on the page in the proper stacking order so that the reading order is correct. A tedious process that wouldn't be necessary if Adobe delivered. This is a huge fail. I hope Adobe fixes it soon.
Did you ever find a work around to this issue? I'm having a similar problem that I can't seem to resolve (Untagged annotations outside document frame in PDF?). What's weird is that I never ran across this issue in earlier exports of the same document...
IT does not work because you does not use the hyperlink panel to create the URL. THIS IS A MUST!
avoid forced line breaks.
I believe that I have resolved some of these issues via work-arounds. My last set of PDFs were created in DC and were relatively painless.
- New Template: Created just in case it was corrupted in some way.
- Articles Panel: My documents are set up with three separate stories. These separate stories are dragged to the articles panel in the following order just before exporting.
- Title Page
- Table of Contents Page
- Rest of Document
- Hyperlinks: Very few hyperlinks show a green dot (despite working in the resulting PDF). I've found that it is best to deselect the Shared Destination. Even though I directly copy and paste the entire link URL into the appropriate field, it often becomes truncated. These are usually the hyperlinks that are not working in the PDF file. It seems that these are always the excessively long links (for me, quite common with Medicare resources).
- Table of Contents: I use the same template for two different documents and therefore have two TOC layouts that reside off to the side when not in use. Each TOC layout maps different headings to the TOC headings. Each of these TOC layouts is saved under a different name.
- TORU: I usually require little work here. Mostly I've found that my H3 styles are never identified correctly and must be fixed.
I was recently dropped back down to Acrobat 11 by our security people so I'm not sure how my improvements are going to work in Acrobat 11. I had found that DC was much easier to use from a Section 508 standpoint and will be submitting the paperwork to see if Acrobat DC can get approved.
I hope this helps!
Hi Willi, I appreciate your feedback but I do use the hyperlink panel so this isn't the issue. Thanks though!
4 people found this helpful
So, I figured out a workaround for the tagging issue. Go into the content panel where the failed annotation link element is listed. Right click on the element and select "Find..." Then in the window that opens select "unmarked annotations" and click "Find". Then click "Tag Element" and select "Link". It'll work through all the link tag errors on the displayed page - just keep tagging them as links and when you've got them all done close the window. Resolves the error message and links remain totally functional. Hope this helps!
Thanks so much for this...I thought I was going to lose my mind figuring this out...
JMcCu, I've used that method often enough to repair the failed annotations but it doesn't address the cause of the problem, which Adobe really need to fix in InDesign or Acrobat or which ever combination is causing the error. I've also posted it as a bug report.
An alternative repair was to delete the hyperlinks from the Hyperlinks panel in InDesign – no more error message and Acrobat somehow still seems to recognise the URLs as hyperlinks, at least in a simple example containing only one web address and one mailto link. Still, it's another bandaid solution, not addressing the root problem.
Deleting the hyperlinks from the hyperlinks panel is not viable if, like SFS-DPS, you have long URLs that break across lines (which we also frequently have to deal with), as InDesign/Acrobat tend to break these links into two links, neither of which work. Same problem also frequently occurs with URLs with some punctuation marks – InDesign or Acrobat chops off the end of the URL so that it no longer works. You then have to use the Hyperlinks panel to create the URLs so that you can paste the entire URL into the URL field – you can't simply leave it up to the export process to pick up the links.
I've found that having "Shared Destination" ticked causes problems (particularly long delays while InDesign "thinks" about hyperlinks) so I never have that ticked anymore. Would be great if this could be the default rather than the other way around (yes, I've report that as a bug also).
I've found that the failed annotations error message seems to occur frequently with hyperlinks in anchored text frames and generally if I can thread the frames instead of anchoring them, that seems to resolve most failed links, but not all. But again, this is a workaround, not fixing the root cause.
thank you sooo much. This issue needs an easier fix. Adobe please note. So many accessibility features need simplification.
I have to say, the whole process of creating an accessible PDF using Indesign, is very frustrating. I've spent countless hours trying to learn how to do this and it's amazing how counterintuitive it is. If I create a hyperlink in my Indesign file, then export as tagged PDF, why should I have to do anything in Acrobat to make that link accessible? And don't get me started with reading order. I've tried adjusting the reading order in the Articles panel, as well as the Structure panel within Indesign, and when I export to PDF, I still have to reorder everything in Acrobat. These are just some of the problems, there are many many more.
Regarding reading order, I have long given up on the Articles panel. It is useless for reading order, or at least was on the last version I tried. I use https://www.rorohiko.com/wordpress/indesign-downloads/framereporter/ to set the stacking order, which defines reading order, then I don't need to adjust in Acrobat and the reading order is set for multiple exports.
This helped, thank you!
I have the same problem with PDFs generated from Microsoft Word so it's not just an InDesign issue - more of a PDF generator issue. I'm about to give up.
Attempting to bring this discussion up to date.
- With the huge improvements for accessibility in CC:2018 (13 and 13.1), are folks still having the problems with missing annotations on hyperlinks?
- How about reading orders? Now that we can anchor text frames, tables, and groups into a threaded story, has this improved the TAG reading order in your PDFs?
- How about the architectural/construction reading order in the PDF? (That's the Order panel in PDF.)
Would like to know how these issues affect InDesigners using the latest version.
Annotations: We've found a huge improvement since CC:2018 and haven't had problems in a few months. Some tips to improve them:
- Don't put a hard return/enter within the URL when it breaks to a second line. This breaks the content into 2 separate paragraphs of content, which is incorrect for any technology, let alone accessibility.
- Avoid using a shift-Enter / line break within a paragraph, too. See if there's another way to correct the wrapping of the URL to a second line, and use the shift-Enter as a last resort. It works, but...
- Sometimes the URL's breaks can be controlled by applying a No Break to sections of the URL. Two default Characters styles I put in my styles panel are No Break and Hyperlink-NoBreak. And I use them liberally throughout my layouts.
- Ensure you've selected the entire URL before creating the hyperlink. I know, it's obvious, but when we're in a hurry we often miss the last character or grab the end-of-line punctuation by mistake.
Our team has been using InDesign to create accessible forms. (Exported to PDF). Most of our team has version CC 17 18.104.22.168 X64. Using this version- we are able to create articles, anchor form fields etc and create an accessible PDF form. However- a few members of our team have InDesign CC Version 13.0.1X64. Using this version- when exported to PDF the form field tags do not carry over. Is this a bug? Is there an update available? Or should we just downgrade back to InDesign CC 17?
Accessibility and Policy Unit
InDesign 13.0.1 does produce the form field tags.
Make sure you've anchored each form field into the text thread, such as:
First Name [anchored text field]
Last Name [anchored text field]
No annotation errors, either.
That is what we did. We exported from the computer with 13.0.1 and got no form field tags. Emailed the In-Design file to a user with the CC 17 older version, exported the same way and it exports with all the correct form field tags.
But did you anchor the form fields into the text flow?
There was a change in 13.0.1 in how it handles form fields.
Make sure they are anchored into the text flow (as in dragging the little blue anchor box on the field frame and dragging it into the text).
13.0.1. also correctly places the form fields at the correct location in the Reading Order. earlier versions do not and instead stack them at the bottom of the RO. They then require dragging into position in Acrobat, a very painful experience!
1 person found this helpful
I just tested this again and all is fine. But from your screen capture, it looks ok, too.
So this might be a bug.
But try the usual steps of trashing your preferences, and if necessary, uninstalling and reinstalling the software.
If it still continues, then log a bug with Adobe in the User Voice forum at Adobe InDesign Feedback.
I do accessibility from InDesign every day and can state that it works...well, at least it SHOULD work. Pretty perfectly, actually.
I too am starting to experience 'tagged annotations fail' with my linked contents menu to different pages in the document. I have never experienced this particular error before and I have been creating accessible pdfs for the past 2 years.
OK, I mis-spoke (or mis-typed) earlier in this thread.
Form fields in InDesign had some bug fixes in the last release, 13.1 -- not 13.0.1 as previously stated.
For those having annotation problems as well as tagging issues in the exported accessible PDF, be sure to upgrade to the very latest version, 13.1. And please let us know if this improves the workflow for you.
Then I suspect it has to do with how the form is created in InDesgn, missing something here or there.
If you can, upload a copy of your INDD file and I'll take a look at it. Don't need fonts or graphics, just the INDD. Or the part of the INDD that has the form fields.
Zip and upload it to a public DropBox or other shared file exchange and post the link here so we can grab it. (This forum doesn't allow attachments or uploads.)
It can be confusing, but remember that the Articles panel only sets the TAG order. The order in the Layers Panel sets the the read, or Reflow order. Both have to be logical.
What I noticed is that while the Acrobat Accessibility check will be correct, if you fix he Tab order first (always needed) and then drag items in the order panel, the Tab order is confused and will flag most links...