Hello all,
I have been working on making a monthly newsletter template for the Research Center I work for accessible to the WCAG 2.0 A standard. Here is a sample (not-accessible) version of the newsletter for reference – https://socialsciences.uottawa.ca/crecs/eng/documents/ImpactSummer2013-web.pdf . I’m working in Adobe InDesign CS6, and I’m trying to create a template that requires no further modification in Acrobat once it is exported from InDesign. I’m running into a few different problems, and I’m not certain which ones are bugs and which ones are caused by a lack of understanding on my part:
-When I try to move things into the correct order in the tag structure of the document (particularly if I try to move it to a higher level in the hierarchy) the object I’m moving will appear to be deleted. Is there a correct way to move things around the hierarchy without having that happen?
-Indesign seems to tag text and text boxes separately, so that I end up with text that is tagged as <p> first as regular text and again as a text box. Will that cause issues with screen readers? Should I try to tag text boxes or individual bits of text?
-In PAC 2 my template generates 25 “Natural language for text object cannot be determined” errors, mostly on page numbers. I have each page number tagged as an artifact, and I am not clear on how to fix this problem.
If anyone has any workflows, answers to any of my questions, or general advice, I would very much appreciate hearing it. I have spent quite a while trying to fix these errors myself, but I haven’t found any fixes or context specific how-to articles online.
Thanks!
-Jon
.
