Hi
I am using InDesign to author documents. I have my styles mapped to tags.
As part of the work I do we design the artwork for printed forms. This artwork uses inline text boxes to represent form fields. Some of these inline text boxes/form fields contain little bits of text (such as an address form field that includes the text "postcode/zipcode") while others are blank.
Every text box is shown within the InDesign structure panel as a "story" tag. Any text or images within a text box are tagged accordingly (P, H1, H2 etc)
So, the InDesign structure panel for any form we design will show a "Story" tag for each main text box (i.e the text box that contains all the questions and form fields for that section). Within a main text box there are "P" tags for each question, and further "story" tags for each corresponding form field/text box. Finally within each form field/text box there is a "P" tag for any text within that form field.
The problem comes when I convert the file as a tagged PDF for publication on the internet. Acrobat has no problems with the main text boxes and sets these up as a "story" container (as per InDesign). However, when it comes to the inline text boxes/form fields it changes these from "story" containers to "figure" tags. Therefore every form field on the document has been tagged as a "figure". What I actualy want is for the inline text boxes/form fields to be tagged for what they are -"story" containers either empty or with "P" text.
My question is - why has this happend? And what will this mean for screen readers?
Thanks
Tim
"Artwork" - perhaps some specific tool/palette that lets you drop in the box - but, coming from this, at some fundmental level in the dance of 1 & 0, whatever is placed is a child of an "illustrative" parent element in the InD application.
Rolled out as a Tagged PDF, any "illustrative" parents (as it were) would be expected to be treated as the in-line structure element in the PDF's structure tree.What does it mean to users of AT?
They will expect <Figure> to have appropriate Alternate Description ("Alt Text").
Keep in mind that "Story" will be role mapping to a grouping element in a Tagged PDF.
I suspect that you will have to reconsider your InDesign layout/format
and the logical hierarchy of your semantic content to harmonize it
with the criteria associated with Tagged PDF (as described in ISO 32000).
fwiw -
There some links to Adobe InDesign/Accessiblity information at this thread:
.
http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=1562
Regardless of what is used for the authoring application, if the output PDF is to be Tagged PDF (for whatever reason)
you'll want Adobe's free release of the IS0 32000 Standard.
See Leonard Rosenthol's AUC Blog article:
http://www.acrobatusers.com/blogs/leonardr/adobe-posts-free-iso-32000]Adobe Posts free ISO 32000
.
The PDF/UA (Universal Accessiblity) ISO document (ISO 14289) is working through the process to approval as an ISO Standard.
For those who would be providing "Accessible" PDF this will be something to have on hand for study and reference.
See: http://webaim.org/discussion/mail_message?id=15702]Duff Johnson's WebAIM E-mail List post
.
Be well...