Tagging Acronyms/Abbreviations in Indesign for an accessible pdf

I am trying to figure out the proper way to tag an acronym in an InDesign file to be properly read aloud in accessible pdf. Currently as it stands, the acronymns are being read as words instead of individual letters ( ex. APR is trying to be pronounced as 1 word). The only way I can think of is to outline that text and give it alt text, but this doesn't seem to be the most efficient way, especially since this acronym reoccurs throught the document in the middle of paragraphs. Also, when this is tagged, should it be the full phrase rather than the acronym that is read aloud, such as APR vs Annual Percentage Rate, even if it is defined elsewhere in the document what it stands for?

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.

Similar Messages

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...

Embedding audio into indesign for playback in pdf

Hello, i'm trying to create a pdf book of educational lectures with audio of the transcribed lectures embedded into the pdf so the user can read and listen along as they like. my solution to this was break up the audio into sections and embed using buttons. this way, the user just has to mouseroll over a button in the margin to play the particular section they want to listen to. there are about three sections per page. the downside of this solution is that the audio doesn't keep playing of course, it just plays that section then stops. i'm now wondering if it might be possible to just have one audio file instead of 60, and make buttons (for each section) that open up the file at a particular point in the audio corresponding to the section; in other words (my question), is it possible to make a button that opens an audio file and plays it from a particular point, not just from the start? I would appreciate any suggestions.

no pardon necessary! i need to embed the audio file because it contains the original lecture, that's what I want the reader to have access to while reading the transcription, since the transcription is not meant to substitute for but rather supplement the audio. for example, in the transcribed text I have put "[...]" for segments of the recording that are inaudible. If I put the original audio into the file then the reader has the option of going to that specific section and listening to it themselves. basically i want to create a pdf document of a lecture. I want to be able to highlight important parts of the lecture, search the lecture for key-words, and scan it quickly for specific items of interest, but I also want easy access to the original audio because tone of voice isn't translatable into text (and the tone of voice in this case is important for meaning), and because there are many segments that I couldn't hear, so I'm trying to figure out the best way to link sections of the text to specific sections of the audio.

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.

How do I create an accessible PDF that doesn't generate a "tagged annotations - failed" error on the Accessibility Checker?

I just reported this as a bug to Adobe, as I think it is.
******BUG******
Concise problem statement: URLs generated from InDesign CC failed on Accessibility Checker (problem also exists in 2014)
Steps to reproduce bug:
1. Generated URLs using hyperlinks panel in InDesign. When accessibility report is run, they are flagged as "Tagged annotations - Failed," listed as Element 1, 2, etc. The links are live and clickable.
2. To test, I removed all hyperlinks in Acrobat. It passed the test.
3. Then I used "Create Links from URLs." The links were re-created. Running the accessibility report brought up the same error message.
Results: The links created by Acrobat that actually do work fail the "tagged annotations" report. You have provided the tools to check accessibility, but the program itself can't generate URLs that pass the report.
Expected results: I should be able to easily create an accessible pdf, as your documentation says I can. This, along with the failure of your "articles" panel detailed in another bug report, strike me as a serious problem with InDesign that should be fixed soon, especially given that designers are required more an more to adhere to accessibility guidelines.

I have call out boxes like this: All the links work correctly but they are divided with a tag for each line:

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!

Looking for Accessible PDF creator

(I'm posting this on behalf of my employer. I looked through terms of service and this sort of posting doesn't appear to be discouraged. If it is, let me know and I'll remove. Thanks!)
Pacific Educational Press is seeking people with advanced knowledge of Acrobat Pro 9 to help us create an Accessible PDF of a Math textbook.
Using Acrobat Pro 9, the qualified candidate will need to convert an ordinary PDF file of a math textbook and convert it into an accessible PDF file that can be used by the visually impaired (using PDF-friendly speech software).
The PDF document has numerous design aspects to it and the person would need to be able to map out the correct reading flow for the speech function of the Accessible PDF.
The document would need to include cross-references and tags for alternate text (to describe the content of photographs, formulas and diagrams).
The person would need to have an understanding of high-school math.
The person would need to begin working immediately and complete the project by April 9.
If you are interested, please send a resume highlighting relevant experience. You will be asked to create a sample PDF to show that you have experience using Acrobat 9 Pro.
No phone calls please.

A Math book eh?
Equations/Formulas - fun.
Regardless, you will want the right "tools" (hardware as well as software).
Specifically, work machines with stand alone graphics card (at least 250MB - more *is* better).
If you are authoring in Word, consider Netcentric's "PAWS".
Might be worth some upfront trials of Word out to tagged PDF via the Office 2007 Save As to PDF.
It has improved since its first release.
Alternatively, augment Acrobat Pro 9 with Netcentric's CommonLook.
The authoring application used will have a significant impact.
Authoring in a page layout application?
There are several good ones but, InDesign looks to have the best tag management.
Tag management and the ability to "stage" for accessibility in the authoring file is significant advantage.
But, for any large, living, technical - Nothing better than FrameMaker.
On the whole, rather pleasing tag management.
Also, does tables like nothing else..
Add to this the "Book" feature of FrameMaker & things get better.
Actually, your job is just what Adobe's Technical Communication Suite is all about (but that's getting OT).
Do not rely upon Acrobat's Read Outload.
Rather, QC PDFs via JAWS, Windows Eyes, NVDA.
n.b., CommonLook gets good reviews on its ability to QC the PDF.
You might want to consider a post to Adobe's Acrobat User Community "Job Board"
as it may broaden exposure to your request.
http://www.acrobatusers.com/forums/aucbb/viewforum.php?id=37
The "tos" is at:
http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=19437
Good Luck with your endeavor.
(just a end-thought - May want someone to spot check as the project goes along.
Karen MCCall of Karlen Communications (out of Canada) may be one of the individuals that could help with such. Certainly there are others - she comes to mind as she has the knowledge/experience and is out of Canada.)
Be well...
Message was edited by: CtDave

Alt tag rollovers in accessible pdfs

How can I make the alt tags for vector images (paths) show up upon rollover in my accessible PDF files. My alt tags show up for all raster images, but not for any eps, ai or png files... Is there a fix for this, either in InDesign or in Acrobat XI... a fix that does not involve using raster for everything please!

UPDATE:
I have spent a long time trying to find an answer to this to no avail. I have finally contacted Adobe Tech Support and explained the issue that concerns me and I have had a response from a senior expert on InDesign/Acrobat/Accessibility.
The issue is as follows:
When you prepare an InDesign document so that the generated tagged pdf is fully accessible for screen readers and the like (create TOC, include bookmarks, add document structure, tag untagged items, map styles to tags, tag uneccessary content as artifacts, include alt tags for images etc.) the bullets in bulleted lists cause the pdf to fail the Full Accessibility Check in Acrobat Pro. The full accessibility report will flag bullets as 'Inaccessible Page Content - the element is not contained within the document structure tree'. This is acceptable from the targeted end user audience (viz those with impaired vision using screen readers) because , as Acrobat states "Content that is not attached to the structure tree will not be available via assistive technology like screen readers." Well you don't really want the screen reader saying "Bullet" or similar everytime it comes across one, do you?
The problem is that the pdf "fails" the full accessibility check and when you are being paid to create fully accessible pdf's, this scares the client somewhat.
The solution:
I explained the above to the Adobe expert and asked if there was an efficient way, in InDesign CS2, to tag all "bullets" as artifacts so that they would be ignored by screen readers AND be seen as artifacts by the Acrobat Pro Full Accessibility Checker and hence pass the check. His answer was NO. I said in the past I had tediously, laboriously gone through the documents in Acrobat pro and marked every bullet as 'background' (= an artifact) to make it pass the Full access checker successfully. Surely, I asked, there must be a simpler way to do this? No, was his answer! "It's extremely cumbersome... but it's the only way"
Aaaahhh.

I am having problems exporting to PDF using InDesign for Mac.

Hi all!
I just started using the Creative Suite on Mac and have run into a couple problems. One is that when I set up a document in InDesign using "Facing Pages" and then export to PDF, the document exports each set of "Facing Pages" as one singular spread (my 20 page InDesign document becomes a 10 page PDF). Once it is a PDF, there are no page break lines in the center of the spread to indicate that they are two separate pages, and when I try to set up viewing preferences in Acrobat (single or double page), it too recogrnizes each spread as a single page.
When I used to do this in InDesign using Windows, whether I exported to PDF or printed to PDF from a document set up with "Facing Pages," each page would still be considered separate once converted to PDF (20 page InDesign docment becomes a 20 page PDF).
This also leads me to my next question : I see that on Mac, there is no option for printing to PDF, but I notice a quality difference specifically when it comes to linework (vector information) that has been "placed" in the document from Illustrator. Is there any way to achieve the quality of printing to PDF on Mac?
Thank you in advance!
Gabby

Hi Bob, I just tried your suggestion, but the interactive PDF is in spreads by default, no way to change the setting. When I choose to view by single page in Acrobat, it displays a single spread.
When I choose to view by spreads, it displays 4 pages, two spreads. That's the topic of this whole discussion, I believe. I do own CS 6 at home, however my employer supplied me with CS 5.5. And I have very little, if any, influence on purchasing.
So, I have no good way to make an interactive PDF (with differing recto/verso headers and footers), that is accessible and shows the correct header/footer. It's either single pages (with one header/footer), or recto/verso headers/footers but PDF only as a spread, as well as I can tell.
Unless you know something else I can do...
Best, Marilyn

How do I use an Edge Animate project with SVG files in InDesign for DPS output?

Is there any way to include an Edge Animate web content using .svg files in InDesign for output to DPS?
Edge Animate works great with InDesign, except for when you're using SVG files. I've worked with SVG files on the web successfully (writing .htaccess files and such), but it seems like InDesign doesn't like them.
This is pretty important because I don't want to have to design multiple renditions on the DPS suite. Currently I have it setup as a PDF format (DPS) and that scales all of the vector-based type perfectly. It would be wonderful if the animations could also be in a vector format so that when the iPad (3) users see the designs, they will scale naturally through the PDF framework.
Any advice would be invaluable.
Thanks!

moved to the DPS forum....

I need to make a pdf document, made in photoshop, 'page turn' and then add it to my website. I know I can do this in indesign but indesign will not open pdf files for some inexplicable reason. Any ideas how I can do it without completely starting again?

I need to make a pdf document, already made in photoshop, 'page turn' and then add it to my website as an e-brochure. I know I can do this in indesign but indesign will not open pdf files for some inexplicable reason. Any ideas how I can do it without completely starting again?

Hello waitingone,
please try this (all terms are translated from my German programs to my best knowledge):
1. Did the creator of the pdf file enable the import options?
2. See import options: choose an other visibility option for your layer.
3. Let you show the import options and click into one with a black background and try these out (often a gray is selected).
4. See trimming: try the different modes there. Often works: "Media".
5. Is the pdf file (eg from Word) correctly created?
6. Is the PDF file protected? >>> no import possible.
7. If that does not help, store the pdf file in Acrobat, repair possible errors, run the PDF Optimizer before placing in InDesign.
Good luck!
Hans-Günter

b and i tags not working in StyleableTextField for mobile development

I'm trying to dynamically produce TextArea instances in a Flex mobile app that implement html formatting. I've made a lot of progress, but simple and tags are not being rendered correctly.
My current hypothesis is that I need to embed the italic and bold fonts. I am currently not embedding fonts for these particular TextArea instances at all -- they are rendering using the system font. In my previous experience, this eliminates problems with rendering and text. However, when deploying on mobile platforms, I don't know for sure if there is a bold or italic system font natively available.
If I need to embed the bold and italic fonts for the tags to process correctly, does anyone know which font(s) I should embed and how I should name them so that the html will be able to find them and render correctly? I am applying a CSS to these TextArea instances in the full app, so I can do any font embedding there if necessary. I am planning to compile this app for both iOS and Android, in case that makes a difference.
Below is a simplified example of the code I'm using. The TextArea that is generated is formatted honoring the tags, but ignoring the and tags.
Thanks in advance for any help.
import mx.events.FlexEvent;
import spark.components.TextArea;
import spark.components.supportClasses.StyleableTextField;
import spark.skins.mobile.TextAreaSkin;
protected function application1_creationCompleteHandler(event:FlexEvent):void
 var textArea0:TextArea = new TextArea();
 textArea0.setStyle("skinClass", TextAreaSkin);
 addElement(textArea0);
 var styleableTextField0:StyleableTextField = StyleableTextField(textArea0.textDisplay);
 styleableTextField0.multiline = true;
 styleableTextField0.htmlText = "bold italic normal";

Huh! I tried tracing the htmlText property after formatting, and the bold and italic tags are not there anymore. Unexpected, but consistent with the results. Thanks for suggesting that test. Here is the line where I assign the htmlText property:
styleableTextField0.htmlText = "normal italic bold <a href='http://www.google.com/'>link</a>";
Here is the section where I create the StyleSheet and assign it to the StyleableTextField:
var styles:String =
"@font-face{ fontFamily: Arial; src: url('assets/fonts/Arial.ttf'); embedAsCFF: false;}" +
"@font-face{ fontFamily: Arial; src: url('assets/fonts/Arial Italic.ttf'); fontStyle: italic; embedAsCFF: false;}" +
"@font-face{ fontFamily: Arial; src: url('assets/fonts/Arial Bold.ttf'); fontWeight: bold; embedAsCFF: false;}" +
"a { color: #FFE043; textDecoration: underline; } " +
"a:active{ color: #ffffff;}" +
"b{fontWeight:bold; fontFamily: Arial;} " +
"i{fontStyle:italic; fontFamily: Arial;}";
var myStyleSheet:StyleSheet = new StyleSheet();
myStyleSheet.parseCSS(styles);
styleableTextField0.styleSheet = myStyleSheet;
And here is the trace statement
trace( styleableTextField0.htmlText); // <TEXTFORMAT RIGHTMARGIN="21" INDENT="10" LEADING="2">normal</TEXTFORMAT><TEXTFORMAT RIGHTMARGIN="21" INDENT="10" LEADING="2">italic</TEXTFORMAT><TEXTFORMAT RIGHTMARGIN="21" INDENT="10" LEADING="2">bold</TEXTFORMAT><TEXTFORMAT RIGHTMARGIN="21" INDENT="10" LEADING="2"><A HREF="http://www.google.com/" TARGET="">link</A></TEXTFORMAT>
Lots of code modification going on behind the scenes, it would seem. Any idea as to why the bold and italic tags are being stripped out when the formatting process happens? Any idea of what steps I could take next? Thanks for all your help so far!
BTW, here's a screen capture of what the text looks like at this point:

Which is better software for brochures and PDF forms ? Photoshop or InDesign ?

Which is better software for brochures and PDF forms ? Photoshop or InDesign ? and why ?

If you are going to be making a lot of brochures, with photos, you probably want both. Photoshop to edit the photos, and InDesign to assemble and layout images with text.

InDesign for wireframing websites?

Do any of you use InDesign for wireframing websites? I need to create a wireframe for a site. I was all prepared to do it in Fireworks. Fireworks has some fantastic features, but I need better PDFs than what it can export. (I tried every setting I could think of but PDFs created from my wireframes always looked fuzzy -- I guess Fireworks can't export vector into a PDF.) So next up: I was considering Illustrator. Then, I saw something on InDesign Secrets about how some folks use InDesign for wireframing. And I do know InDesign better than Illustrator. So wondering if I should try it that way. Do any of you use InDesign for that purpose? If not, got any recommendations for software for wireframing (something that will give me better PDFs than Fireworks)?
Thanks, Phyllis

Hey Phyllis!
So recently I've created a REALLY basic wireframe using InDesign. I basically created the visual direction so my client could easily understand how the Web site would flow. In other words, boxes with page names and lines connecting them. It can be really simple if all you're trying to do is show the site's direction.
From there, we will create the in-depth visual layout for the splash page, home page and a global page (This is where I utilize Photoshop/Fireworks/Illustrator or Flash). This is where we will dive into color schemes, and layout schematics. In our case, this a site where we have no logo established, but have the overall concept in place, so that's why we haven't decided on an overall theme just yet. Still working out the kinks!!
Hope this helps!
Jazz

InDesign for a $25 a year fee?

Just bought a new macbook pro and in an email I can no longer find I read that you can use ID (InDesign) for a fee of $25 annually?!? Is this right and if it is can someone tell me how the heck to buy it.
On another note how much is PS (Photoshop) and (AAP) Adobe Acrobat Pro?
These are the only three pieces of software I need so I don't want to have to pay the $29.99 per month for all applications.
HELP.

i don't know a bout this price ($25 annually) the link below show you the per month subscripiton price.
https://www.adobe.com/products/catalog/software._sl_id-contentfilter_sl_catalog_sl_softwar e_sl_allsoftware.html

Tagging Acronyms/Abbreviations in Indesign for an accessible pdf

Similar Messages

Maybe you are looking for