Copy link to clipboard
Copied
At my job, at a large metropolitan area transit organization, I am currently attempting to convert our bus schedules from inaccessible, text frame based pdfs to pdfs that are fully tagged and where the schedules are in navigable, accessible table structures. The documents are designed in InDesign. Our Graphic Designer and Desktop Publisher will be the ones utilizing my design/ template to update and author new schedules so I am trying to make the process as automated and “built in” as possible. I have successfully converted the current design into a tagged and tabled document with a few issues.
The issue I am asking for help with concerns a document I am designing that has a schedule table that spans two pages. The header row for the table has anchored text frames as text ( the design I am working with has table header labels that are at 45 degree angles and don’t fit into the table). When I export the tagged PDF, the header row, which is repeated on both pages, does not appear as the first row of the table, instead that row is now about half way down the tag tree after the last row of the first page and the first row of the last page. The tagged elements, though, are the elements at the very beginning of the table. Based on your expertise, would you know why this is happening?
Since I am developing this document as a template for future schedules, ones that will be edited by other designers, I am trying to put as much of the accessibility work in the InDesign file as possible so that there is less items and less complexity in potential remediation of the document in Acrobat Pro.
Copy link to clipboard
Copied
Check your order in the Layer (expand the Layer the Table is on), this anchoring of headers is not a good way to work as it will be difficult of tagging them as TH and messes up the order . Anyway, this kind of table remediation is always necessary in Acrobat. In your screenshot I see no <THead> nor <TBody> parts so it is not tagged correctly it seems, but that is a bit of guessing without seeing the actual file...