WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Untagged PDF doc with table structure

for

From: Ryan E. Benson
Date: Feb 19, 2015 1:57PM

Hi Olaf,

>it does handle <TH> quite well (at least for column headers).

Not sure why you think this, since it is not a supported tag, as you
mention below.

>nope. What you actually do is do assign a certain tag to your style sheet
which then gets used during export (and via role mapping in the resulting
PDF.

I was trying to cut out the jargon. Most people do not know there are
styles and tags within inDesign, in my experience. If they just make a
style, and lazily name it h1, that gets exported and mapped to P - in the
two sample files I tried - in CS6. The user has 3 options. 1- properly
named styles. 2- Open up the style, choose the right tag via export tag
options. 3- open the tags pane, use the map styles to tags option, and map
it. This assumes the user opened up the structure pane, and used the "add
untagged items" option. This also creates the known tags to inDesign -
which is 9.

> InDesign supports a a lot of standard PDF tags.
9 of 34 is 26%. Not sure if you call that a lot. Now if a user sets up
their document properly, and use the built in features, of course that goes
up. In my experience, working with designers, who have a degree, and
trained inDesign, don't do or know this.

--
Ryan E. Benson

On Wed, Feb 18, 2015 at 6:13 PM, Olaf Drümmer < <EMAIL REMOVED> > wrote:

> Hi Ryan,
>
> On 18 Feb 2015, at 23:50, Ryan E. Benson < <EMAIL REMOVED> > wrote:
>
> > InDesign only recognizes a handful of standard PDF tags. I can't find the
> > list right now, but I am pretty sure it is in the help. InDesign knows
> > <Table>, <Tr> and <Td>, for example, but not <TH> or something like
> that.
>
> it does handle <TH> quite well (at least for column headers).
>
> > PDF tags are case sensitive, so if you create an h1 Tag for your inDesign
> > document, it gets mapped to the <P> tag in the PDF. However, creating the
> > H1 tag in inDesign, it correctly gets mapped to H1 in the PDF.
>
> nope. What you actually do is do assign a certain tag to your style sheet
> which then gets used during export (and via role mapping in the resulting
> PDF. The list offered here consists of only H1 through H6 and P (yep,
> that's it, except for <H> which you do not want to use, and 'Artifact'
> which is not a tag, but can be handy at times). Most other stuff is just
> handled properly by Indesign, at least for stuff like lists and tables
> (with some limitations - e.g. no row headers, no complex table structures)
> and footnotes and figures and links and (CS 6 or newer) form fields.
>
> Some of the glaring omissions are lack of support for table of contents
> (TOC / TOCI), something as easy as Caption, or BlockQuote, Quote, Formula
> (accompanied by lack of support for something like MathML) and a few others.
>
> So the statement
> > InDesign only recognizes a handful of standard PDF tags.
>
> has to be turned into its opposite:
> > InDesign supports a a lot of standard PDF tags.
>
> with the following addition:
> > With some very unfortunate [seemingly easy to implement/support]
> omissions, like support for Caption, or BlockQuote, Quote, Formula and a
> few others.
>
>
> Olaf
>
>
> > > >