Text Flow in ePUB and Accessible PDF

I have a newsletter in InDesign. I have all the text flow marked. Each article is a separate "story". Story1 flows onto page 2, with the text flows linked correctly. On page 2, story2 begins in the text box below the end of story1.
So on page 2, why does accessble pdf read story2 before the second portion of story1?
I have the same behavior in the version extracted to EPUB.
Any ideas what I am doing wrong? or how I can correct it without having to create a single column of text throughout?
Thank you,
Joyce

I've never seen that. In both accessible PDFs and EPUB, when I export all of a story will be read before going on to another object.
What version of InDesign are you using? If you're using InDesign CS5.5 or later, you can use the Articles panel to set the reading order for accessibility (or for EPUB).

Similar Messages

Sync Text alignment in HTMLEditor and a PDF generated using FOP

Hi,
How to sync text alignment in HTMLEditor and a PDF generated using FOP ?
I tried setting the dimensions of HTMLEditor and PDF in pixels by calculating the size in Pixels for A4 paper size with a particular dpi value.
Have done the font settings as well. The problem is I see uneven line cuts in the PDF as compared to HTMLEditor.
Thanks.

It's not a realistic expectation. You are expecting the PDF produced by whoever provided your FOP implementation to observe exactly the same typographical rules as HTMLEditor. Basically it won't, and there is no way to enforce it. Line breaking/hyphenation/word spacing algorithms can be of great complexity. You are expecting two systems that aren't specified to agree, to agree.

Text documents w/symbols and also pdf's

I am trying to incorporate my trademark, logo design and symbols. Program will not download microsoft word docs. Can adobe 1 page pdf files be downloaded into the beginning or end of a video? Thank You.

Don't let the newness of the program get you down.
Titler is a pretty powerful little application. However, it does have some limitations. I use it for most of my simple Titles, but rely on other programs for something more involved. I'll do the text in Word, or WordPerfect (to use Spell Checker), and then do Copy/Paste operations to either Illustrator (and then to PS), or Photoshop to get my final output. For me the only question is when to I go to those other applications. I'm pretty quick to jump out of PrPro's Titler, but much of that is because I love working in PS and AI for their control.
Good luck,
Hunt

Cannot open a epub and a pdf file

I have ricently purchased a new ebook. While downloading the ACSM file I'm getting a message on my reader (Pocketbook 602 pro) that the "file is damaged or protected", but I did get a EPUB file that doesn't open.
The strange thing is that after this happened, I'm also unable to open a PDF file of a book I'm currently reading, and opened many times. I'm suddenly asked to enter a password, but I don't know password of what!? My password for Adobe doesn't work.
Please help!

Most likely, a setting on your ereader is causing the issues. Check the
User's Guide for the Pocketbook and see how it treats DRM-protected files.
Also, have you linked to their website recently for any software updates?
=========

EPub Scanned Images without Text Flow

I am working on an ebook that has lots of complex illustrations, tables, captions. Scanning the images by converting them to JPEG is needed in order for the illlustrations and text to not move. Text flow is an option that I will not be able to offer.
How do I create an ePub book with scanned images without text flow. I did it once, but cannot remember how to do it.

TabulaMentis wrote:
The ePub version of the ebook will have a fixed layout without text flow. You mentioned that I buy someone's book, but this is a simple question. Why does InDesign not make it easy to convert an InDesign CS5.5 file into an ePub file with fixed images without text flow. Amazon and Google have lots of those types of ebooks in ePub format for sale with fixed images without text flow?
Because if you read anything about creating EPUB files, you'll find that that's NOT how they're intended to be used.
For example, in the first paragraph of the Wikipedia article about EPUB, you'll read:
"EPUB is designed for reflowable content, meaning that the text display can be optimized for the particular display device used by the reader of the EPUB-formatted book. The format is meant to function as a single format that publishers and conversion houses can use in-house, as well as for distribution and sale."
So that's why InDesign exports EPUB the way it does.

Acrobat vs Livecyle - which is better for making accessible PDF's

I am having a very hard time making my PDF accessible. The source program I use to create my document is InDesign 5.5. I convert to PDF and am attempting to tag it using Acrobat X. I tried tagging my form using the articles panel in InDesign but it doesnt convert to PDF properly (which i learned at this forum is a system glitch). Someone at work suggesting using LiveCycle but I am not familiar with LiveCycle at all. I thougt it was an add-on extension to Acrobat so I'm confused why someone would tell me to use LiveCycle instead of Acrobat X. Can someone please clarify for me what the diff is between Acrobat and Livecyle. I need to make my document accessible by the end of the week and having a lot of problems doing it but i want to make sure that Acrobat is the best adobe product to use before going any further.
Any help is GREATLY appreciated!

Hi miss forms,
I'm out of the country just now and "on-line" time is occasional. However, here are some observations for your consideration.
All this may sound daunting. It is not (honest). Think of it as becoming a competent cook.
Some study. Some practice then it is Rachael Ray time.
~~~~~~~~~~~
Here's a short take:
Use InD CS 5.5 to master the underlying "form text".
Master content with accessible PDF in mind.
Example - if any "headings" are to be used then use InD built-in paragraph tags.
Output the tagged PDF.
Walk the structure tree. Perform requisite post-processing activities.
Goal is to acquire that well-formed tagged PDF.
Next, build the form fields.
Properly fold these into the structure tree.
~~~~~~~~~~~
Observations:
"... but i want to make sure that Acrobat is the best adobe product to use before going any further."
Currently and for the foreseeable future - if you must provide accessible PDF as a deliverable you must have Acrobat Pro.
You want the most current version and you want to keep it updated.
Currently there is no such thing as an accessible PDF that does not require post-processing by a knowledgeable "warm-body".
As the 'warm-body' you perform the essential V&V prior to release of the deliverable.
While there are tools to help with they still do not replace the 'warm-body'.
"I need to make my document accessible by the end of the week ..."
This could be problematic. Unless you are all ready well versed in what a well-formed tagged PDF is and how to stage it in the authoring file I suspect that you won't have a proper deliverable by 30 November.
Using InD CS 5.5 is 'good' but it is not (as you've discovered) adequately robust for well-formed tagged PDF output compared to the current release.
The output PDF needs manual remediation (only possible with Acrobat Pro).
As to any current authoring application used -
Whatever is used it needs to provide robust "tag management".
Currently the first string consists of:
Adobe FrameMaker,
Adobe InDesign,
(n.b., Adobe has invested significant resources in improving mastering content for accessible PDF and output of tagged PDF InDesign versions released since CS5.5. So, if InD is your requisite authoring application I'd recommend you move into the current release.)
MS Word 2010.
When using MS Word 2010 one can use the MS Save As PDF - XPS configured to provide accessible PDF or use
PDFMaker.
For Word 2010 you'd need at least Acrobat X in order to have a compatible PDFMaker.
Some other applications are also providing for authoring / tagged PDF output (such as Open Office).
Regardless of the authoring application used Acrobat Pro is still need for requisite post-processing (structure tree V&V, cleanup, etc).
What form "type" to use?
I'd recommend Acrobat forms rather than XFA forms.
Accessible XFA forms are possible.
But, As George said - a non-trivial learning curve for the basics. Then comes the learning / practice to develop the accessible XFA form.
If you go with XFA I suggest obtaining the XFA spec that Adobe provides.
Considering the improvements Adobe has made in Acrobat XI for Acrobat forms I'd recommend you use that.
However, if you have an older version you can still get there from here (using Acrobat Pro).
"Tools" considerations:
Common Look PDF - An enterprise level tool.
A plug-in for Acrobat.
Common Look Office Pro
(Pro supports PDF forms (Acrobat forms - not XFA forms)
An add-in / plug-in for MS Office 2007/2010.
Used with Power Point or Word.
Provides check points on mastered content. You resolve identified issues then use it to output a tagged PDF.
Perfom requisite post-processing with Acrobat Pro.
http://www.commonlook.com/CommonLook-office
MS Word 2010
Provides content mastering "coaching" for output of accessible PDF.
PDF Accessibility Checker
A "validation" tool.
http://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac.html
AIIM's PDF/UA, Universal Accessiblity
http://www.aiim.org/Research-and-Publications/Standards/Committees/PDFUA
The "Achieving WCAG 2.0 with PDF/UA" is available.
The Implementation Guides are in the oven.
ISO 14289-1:2012 (ISO standard for PDF/UA)
Available for purchase at ANSI's web store.
ISO 32000-1 (ISO standard for PDF)
Section 14.8 discusses tagged PDF.
Free, ISO approved copy available from Adobe.
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/pdf/pdfs/PDF32000_200 8.pdf
I've tried to harvest accessible PDF documentation Adobe's provided since Acrobat 5.
Have most of it my "eReference Shelves"; but, that's at home.
What's nice about these documents is that you can harvest activity specific information with confidence that it is an appropriate "reciepe".
If interested in adding these to your "shelves" let me know.
Use this forum's PM feature.
Be well...

Using Replace Pages in accessible PDF's

Hi - Brand new to this forum. Hoping someone can help... I have an existing tagged and accessible PDF - needed content update, so did that in Word, created a new tagged and accessible PDF, and used Replace pages to insert the new pages into the existing PDF. Acrobat Help says when you replace pages in a PDF, Acrobat adds the tags from the incoming pages to the end of the tag tree... and keeps the tags for the replaced pages. That didn't happen - the tags from the incoming pages are not there and, in fact, the tags that were in the existing PDF are not there anymore either - now it just says "Warning, empty page". Any ideas?

Hi kvd,
I guess my nomenclature may be presumptive. All I should have said is that the most appropriate method I have discovered for retaining tagging and all other accessibility functionality has been the Combine command. Replace Pages sometimes works and most of the time (lately) is doesn’t. My experience with Insert Pages has not been consistently successful either.
What you mean by a workflow I don’t fully understand. Do you mean an automated action? Unless you consistently use the same page numbers in every document, I don't know how you could automate it. Also, I have not been able to find specific process treatment about combining tagged PDFs. This has been a result of testing and experimentation.
Let me know if you have any other questions.

Replacing pages in accessible PDF's

Hi - Brand new to this forum. Hoping someone can help... I have an existing tagged, tested and accessible PDF - needed content update, so did that in Word, created a new tagged, tested and accessible PDF, and used Replace pages to insert the new pages into the existing PDF. Acrobat Help says when you replace pages in a PDF, Acrobat adds the tags from the incoming pages to the end of the tag tree... and keeps the tags for the replaced pages. That didn't happen - the tags from the incoming pages are not there and, in fact, the tags that were in the existing PDF are not there anymore either - now it just says "Warning, empty page". Any ideas?
Thanks greatly!

Hi Bill@VT,
Thanks for your response. Presently, I have AA Pro XI and Word 2007. I am confused - it seems the Adobe help material is saying different things - my pages say the new tags will come with the new pages, and your pages say not?
I am suspecting some of the problem may be coming from the fact that these documents have been created over many years using various versions of Word and Adobe Acrobat - since I got Pro XI, some pdf's that used to work OK for our people using screen reader technology suddenly don't read correctly anymore. I need to repair anything not working, and I need to create a new workflow process for myself to create accessible Word documents from the start. I'm thinking it may be cleaner to just start over and create all brand new Word documents with accessibility, maybe in Word 2010 or 2013, and then run them through Adobe Acrobat "Make Accessible" function and checker.

How do I create an accessible PDF for Thesaurus with many chapters, from InDesign CS 5.5 and Acrobat

Hi folks,
I have redesigned a Thesaurus (controlled vocabulary for an Agency's archives) in InDesign CS 5.5. I am now preparing an accessible PDF from the many files (using a Book created in InDesign). The front cover, front matter and back cover are not part of the Book, to keep the page numbering simple.
The Book includes two main sections, an Alphabetical display and a Hierarchical display of terms and their relations. I created chapters per alphabet listings, i.e. Alphabetical Display A, B, C, etc. So there are over 50 chapters, including cover, front matter, etc.
I've successfully made the front cover and front matter PDFs after viewing videos here: http://tv.adobe.com/watch/accessibility-adobe/preparing-indesign-files-for-accessibility/ and downloading and using this recommended Action for Acrobat: InDesign CS5_5 Accessibility Touchup.sequ
Several questions specific to this project don't seem to be addressed in the videos, however.
First, I'd like to know if I can create an accessible PDF using the Book function > Export Book to PDF. Or do I need to make a PDF per chapter? The book has over 50 chapters (by alphabet, twice), so creating them one by one will take a lot more time, but I'll do it if that's the best practice.
After creating the PDFs, if I use (in Acrobat): Create > Combine Files into PDF to make one full PDF (over 600 pages BTW), will the final PDF retain accessibility settings? Do I need to run the Accessibility Report again for the combined PDF?
I used InTools.com Power Headers plugin to add a page header that automatically shows the new first term used per page. So, one chapter (with Chapter Title as H1) will have a different page header (which will be H2) per page, however the text flows through the whole chapter. I don't see where to add the page headers to the Article Window in InDesign. Do I add in this order: H1, H2, text (for whole chapter), H2, H2, H2, etc. Will I need to work on the PDF in Acrobat, where pages will be shown, in order to get the correct H2 with the correct text on the page? Am I missing something?
Will I have any issues with Bookmarks that requires a specific workflow?
I think that's about it, though I might run into more questions as I progress through the project.
Thanks, Marilyn

I understand why you need updated running headers in your book. To a sighted reader these serve as a guide to where you are and help you find things quickly. In addition, if you are exporting your data to XML or HTML from the tagged PDF it would also be important to have these in the proper location.
But for accessibility purposes, it doesn't have to be there because the screen reader reads everything in linear order, line by line. No one is looking at the page. A user listening to the screen reader read the page is going to hear this heading, just before the actual word itself. So they will hear the first word on the page twice. It's not the end of the world if it's there, but such headings are not necessary for accessibility unless they are not repetitive and contain information that is not otherwise available.
So I would say, fine if you need them or want them there, it's just one word.
I think you should try exporting your book to PDF (or even just a chapter of the book) and look at the tags panel in Acrobat to see if you are getting the result you want. I can't tell you exactly what you should do to get those results, you are using a plug-in I don't have.
I can tell you I didn't have to add the headers to any article at all, they just automatically export if the other articles in the file are added and you don't select the header style option "not for export as XML."
You may not experience the same results with your plug-in, but I think it will probably work the same way.
Give it a try and best of luck.

Headers and footers in accessible PDF

I have a Microsoft Word 2007 document with headers and footers. When I use the PDFMaker icon to create a PDF for Acrobat 9, I need the headers and footers to be included in the Tags panel and to have a number in the Order panel. However, the header and footer are completely ignored by Acrobat, and treated as "Background."
I sure hope someone has a suggestion about this; otherwise it will be a tremendous amount of work for a long document to add headers and footers into the Order panel and the Tags panel.

The Header and Footer on each page has been designated as an "Artifact".
Standard MO for any competent tag management facility provided with/for the authoring application.
AT knows to ignore artifacts.
An overview of how to fold Header/Footer content into the structure tree open the Tags panel.
From the Options menu use "Find".
Select Find: Artifacts.
When Header/Footer PDF page content is located (the blue box) return focus to the Tags panel.
Select the tag to which the identified content's Container is to placed.
(Upfront - give some thought as to what is to go where in the tree. Fraggled structure trees (bad/improper Tag semantics) can really hose a PDF in terms of accessibility).
On the Find Element dialog, click "Tag Element".
Note where the new Container appears in the structure tree.
Be sure that it and the parent tag are properly placed.
Repeat for each Header/Footer.
Be aware that putting repeating Header/Footer content that, due to being in a Header/Footer, should be an artifact into the structure tree will result in AT presenting the content to the AT end-user over and over again as one moves through the pages.
An almost guaranteed way to really render the "message" intended for the end-user to be drowned out by the "noise".
Such PDFs can be very annoying and thus are, typically, set aside and avoided.
An unintended consequences is the perception that the entity who "owns" the content is, likely, not worth their salt and to be avoided as well.
Best practice — If content is salient to the semantic intent of the document it is properly folded into the text flow.
Be well...

Accessible PDFs from InDesign CS3 and Acrobat Pro 8

Is there a good website or book that explains how to create an "accessible" PDF with text and images (no intaractivity or special fields to enter information)? Maybe a book for non-programmers.
I find a lot of general information and it always states that it's the best to do the tagging from the beginning in InDesign but what else does it ivolve? In what order should I do what?
Thanks.

I'm doing one of the exercises provided by Adobe and have a question (InDesign CS3). I just learned that you can assign the "Artifact" tag to a graphic frame in two ways: Either via "New Attribute" in the Structure window (Articat/TRUE) or by right clicking and "Tag Element > Artifact").
The results are different though. The New-Attribute-way keeps the name "Figure" and adds a Bullet to it saying Artifact=TRUE, while the right-click-option changes it from Figure to Artifact and adds no Bullet.
Is there any difference for the person receiving the PDF and what is the better version (for what)? Thanks a lot!

Pdf reader with text flow / wrapping, for N810

Has anyone installed a pdf reader that allows for text flow (also called wrapping), so that you can magnify a pdf without getting into a left-right scroll situation? Without this feature it seems impossible to read pdfs on this device, except in a pinch. If you found one, what app is it and where did you get it? And are you completely satisfied with it?
TIA

Try checking the download section on
http://maemo.org/
If you need my help or I late with an answer you need, send me a private message
P.S.
Please before doing that, be sure you have already searched the topict on this site about the issue you have. Read Help sections before asking. Describe yor issue step by step with complete details.

Accessible pdf alt text read twice by on-screen reader

We are working on a math text book. We are currently creating an accessible pdf in addition to a text book for people who are visually impaired. We have ordered our text such that the on-screen reader reads the pages in the correct order and have tagged sections appropriately. However, some paragraphs contain several symbols that the on-screen reader cannot comprehend and for those we have made figures and inserted alt text that literally explains the equations. The problem is that the on-screen reader will first read the alt text but then will proceed to read the text itself that we are trying to replace. Thus many paragraphs are read twice. Please advise.

Hi,
Alternate Descriptions:
PDF documents may be enhanced by providing alternate descriptions for images, formulas, or other items that do not translate naturally into text.
But, you have content that does translate naturally into text. So, you get the alternate text entry and the content that is naturally renderable.
Consider use Replacement Text (Actual Text) or, when appropriate for abbreviations/acronyms, Expansion Text.
However, if the characters are naturally renderable, there is no need for any of these.
Do apply the PDF element for "formula" to the equation content.
Only use alternate text descriptions for image/graphic objects present in the PDF.
Avoid having other tagged content being associated with a child tag of a tag that has alternate or actual applied.
You may find having a copy of ISO 32000-1:2008 available helpful.
Obtain a free version oF ISO 32000-1.
http://www.acrobatusers.com/blogs/leonardr/adobe-posts-free-iso-32000
Be well...

I am creating a form on LiveCycle Designer and I am trying to create a form that has a e-mail submit button. When the butten is utilized it attaches the form to the e-mail in an plain text .xml format rather than the pdf format. Is there a quick fix?

I am creating a form on LiveCycle Designer and I am trying to create a form that has a e-mail submit button. When the button is utilized it attaches the form to the e-mail in an plain text .xml format rather than the pdf format. Is there a quick fix?

Hi,
You have the choice between xml or pdf, in later versions of designer you can choose with a dropdown on the email button Object palette, the "Submit As";
In earlier version you had to edit the XML Source and change the format from xml to pdf (or vice-versa);
Regards
Bruce

Accessible PDF files and forms

I am beside myself with the lack of help and/or interest in the Accessiblity area. We have been mandated to make all our PDF files accessible on our Web site. We have been able to master many of the issues regarding tags and form fields, but still have questions regarding updating the original PDFs without loosing the tag structure.
Is there any options on the Adobe site that may concentrate on this area? I called tech support yesterday (Bronze contract), was on hold for 10 mins and got disconnected. After leaving my number, they never called me back again.
HELP
KEN PANTHEN, Albany, NY

Bill
The point was not having to create the tags again in a new file before
replacing the pages containing the form fields in the old file. We have
many forms that get updated right up to the last minute and to go through
the tagging process is too time consuming. We do not use PDF Maker, but
produce all the PDFs directly out of InDesignCS3 to Adobe Acrobat
Professional (Distiller).
Thanks for your reply.
KEN PANTHEN
NYS Tax Department
Information Technology Specialist 2
FPM - Composition Services Unit
(518) 457-1425
(518) 485-7828 (fax)
From:
"Bill@VT" <[email protected]>
To:
Kenneth Panthen <[email protected]>
Date:
06/24/09 11:19 AM
Subject:
Accessible PDF files and forms
I am really suggesting replacing all of the pages. I was thinking that the
tag structure would go with the replacement and you would need to create
the other PDF with PDF Maker to keep the tagging. I may be wrong, but that
was the view I had. If you replace a single page, I am not sure what might
happen since that would generally not be done with PDF Maker.
Since you already have the application process going, it is probably
easiest for you to try the variations on replacing pages and such --
basically what I would be doing.

Text Flow in ePUB and Accessible PDF

Similar Messages

Maybe you are looking for